Feature Request:
Would it be possible to have the Mu editor save a file locally as well as on the CircuitPython target?
Problem Statement:
Developing straight onto the CircuitPython target it great, but it has the risk of losing your code in case something happens to the target board (broken, lost, etc).
Background/Further talk:
I'm thinking that it would be great to be able to have the option to save the *.py files onto the target and onto the local drive simultaneously to mitigate this. There are other ways to solve this problem, such as saving locally then copying over when modified. This could be done manually or through a simple script, however, it would be great to see this as part of Mu.
sethkaz
>All comments
I submitted a pull request with these features this last summer waiting for version 1.1 for the adafruit version.
https://github.com/mu-editor/mu/pull/485
It adds a "Run" button that copies local files to the CPX and also does some library file management.
Keep asking. I'd like to see this included so I don't have to keep updating the systems at our makerspace.
fmorton
on 27 Jan 2019
Related issues
ladyada
路
4Comments
jaustin
路
6Comments
the-stanely
路
7Comments
hwiguna
路
8Comments
probonopd
路
5Comments
Most helpful comment
I submitted a pull request with these features this last summer waiting for version 1.1 for the adafruit version.
https://github.com/mu-editor/mu/pull/485
It adds a "Run" button that copies local files to the CPX and also does some library file management.
Keep asking. I'd like to see this included so I don't have to keep updating the systems at our makerspace.