Bug 489804 - Automatic export/save of backend script file
Summary: Automatic export/save of backend script file
Status: REPORTED
Alias: None
Product: cantor
Classification: Applications
Component: general (show other bugs)
Version: 24.02.0
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Cantor Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-05 22:50 UTC by simon@i2cchip.com
Modified: 2024-07-07 20:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description simon@i2cchip.com 2024-07-05 22:50:04 UTC
SUMMARY
I use Cantor to make worksheets which are then included in Latex documents.
It would suit me well to have Cantor export/save the (octave) script every time that it saves the CWS file, so that I can run them directly from octave.
Comment 1 Alexander Semke 2024-07-07 18:06:06 UTC
(In reply to simon@i2cchip.com from comment #0)
> SUMMARY
> I use Cantor to make worksheets which are then included in Latex documents.
> It would suit me well to have Cantor export/save the (octave) script every
> time that it saves the CWS file, so that I can run them directly from octave.
Implicitly and always saving in another file is not something that most of the users will want to have. We have the option to save as Octave script. Is this not working for you?
Comment 2 simon@i2cchip.com 2024-07-07 20:49:56 UTC
Since my main objective is using them automatically, https://bugs.kde.org/show_bug.cgi?id=489805
My actual need would be met by a commandline commands to exportscript, runscript, exportpdf.

//------
I realise that Cantor can't import .m files, so what I had in mind probably isn't workable, as editing the external .m file would leave it orphaned.