Any way to automatically save my LiveScript .mlx file as a Text-based .m file?
As given here, LiveScript is rather unhelpful for source control in terms of tractability and interpretation.
https://www.mathworks.com/matlabcentral/answers/271488-how-do-i-use-live-script-mlx-files-in-source-control
I like using LiveScript, but want the ease of source control of a text-based file, such as .m files.
Sometimes, I manually save (a copy of) the LiveScript as a .m file, so that the latest changes may be interpreted in git. Is there a way to automatically copy/save a .m file every time I save the .mlx file?, instead of manually clicking some menu options? This is one way I hope I can access the ease of writing in LiveScript while not compromising on the ease of source control.As given here, LiveScript is rather unhelpful for source control in terms of tractability and interpretation.
https://www.mathworks.com/matlabcentral/answers/271488-how-do-i-use-live-script-mlx-files-in-source-control
I like using LiveScript, but want the ease of source control of a text-based file, such as .m files.
Sometimes, I manually save (a copy of) the LiveScript as a .m file, so that the latest changes may be interpreted in git. Is there a way to automatically copy/save a .m file every time I save the .mlx file?, instead of manually clicking some menu options? This is one way I hope I can access the ease of writing in LiveScript while not compromising on the ease of source control. As given here, LiveScript is rather unhelpful for source control in terms of tractability and interpretation.
https://www.mathworks.com/matlabcentral/answers/271488-how-do-i-use-live-script-mlx-files-in-source-control
I like using LiveScript, but want the ease of source control of a text-based file, such as .m files.
Sometimes, I manually save (a copy of) the LiveScript as a .m file, so that the latest changes may be interpreted in git. Is there a way to automatically copy/save a .m file every time I save the .mlx file?, instead of manually clicking some menu options? This is one way I hope I can access the ease of writing in LiveScript while not compromising on the ease of source control. livescript, source control, 2023a MATLAB Answers — New Questions