I note that you had a problem in a wl file where all of the code was commented out. I wonder whether there is a bug here. I had the same problem which was not obvious until I opened the file in an editor. Each line in the code had been commented and thus was unable to use it. I think it happened when I moved the code by cut and paste.

There needs to be
a) a means of seeing this problem and
b) a means of editing the problem out.

The bug was that the cells could not be changed to Code/Initialisation cells within the *.wl format in Mathematica. For some reason even Quit and restart did not enable these cells to change to Code cells but instead remained as commented lines. I could only restore normal operation by editing the lines outside Mathematica.

I have now lost the incorrect notebook and thus am unable to re-demonstrate the issue.

I typically stay away from Workbench since I like to use the full arsenal of possibilities that notebooks afford me. If you don't need a notebook directly then you can program a .m file directly in Mathematica. But I'd argue and ask why one would want to do that when one can work directly and document as one goes along in a notebook. By the way, any Input cells that you do not want to have included in the autosaved .m file in the approach above you can set them not to be Initialization Cells and then they will not end up in the resulting .m file.

Another possible approach to doing what you are describing might be to actually execute a notebook (and by pass the saving as a .m file as I described) on the raspberry pi even though it does not have a FrontEnd open associated with it. This is to use the function NotebookEvaluate on the notebook pointing its argument to the notebook;'s file path. One may have to wrap UsingFrontEnd around the NotebookEvaluate call. That's something that I am just suggesting but don't have the setup to test. Give that a try and let me know if it's something that works with your architecture,

Hi David,

Execute the following in the notebook in quesiton:

SetOptions[EvaluationNotebook[],

  {AutoGeneratedPackage -> Automatic, 
  InitializationCellEvaluation -> False, 
  InitializationCellWarning -> False, 
  StyleDefinitions -> 
   Notebook[{Cell[StyleData[StyleDefinitions -> "Default.nb"]], 
     Cell[StyleData["Input"], InitializationCell -> True]}, 
    Visible -> False, 
    StyleDefinitions -> "PrivateStylesheetFormatting.nb"]}
 ]

Alternatively (I assuem that you are programming in Input cells rather than Code cells), do the following:

Edit the notebook's StyleSheet to modify the Input cell style to make it always an Initialization cell. Then via the Option Inspector for that notebook with its scope set to Selected Notebook set the following options:

AutoGeneratedPackage -> Automatic, 
InitializationCellEvaluation -> False, 
InitializationCellWarning -> False

These details are also contained in a small introductory tutorial that I wrote up a while ago and which I've posted before: I am attaching it here for reference...

--David

Attachments:

HI Caitlin,

My belief/understanding is that this is a positioning change to bring the language aspect of the Wolfram Language into focus and to orient it more broadly beyond its embedding in Mathematica itself.

--David

How could I apply your suggestion of code snippet for my NoteBook ? Should I put it at the beginning of the Notebook and evaluate it, or at the end of the Notebook ? I don't know what to do.

By default, only Initialization cells are saved to .m or .wls uncommented. Place the snippet anywhere in the notebook and evaluate it. It will mark all Input cells as Initialization cells and automatically create a .m file whenever the notebook is saved. No need to manually Save As.