Preview-compile
Brought to you by:
fodber
Menu
▾
▴
#23 Preview-compile
Sometimes it is annoyinfg that LT works directly on an open file. To have a preview, he need to save it, and so the file is changed. If it worked in a temp directory with a copy of the file, then it could ask the user if he wants to save changes in the original file when quitting, if the user didn't already save it.
this has a additional advantage: it wuold not produce unwanted pdf - midi - eps - log files in the original directory.
This behaviour should of course be switchable on and off.
This request needs a bit more elaboration.
What is the use case when it is actually annoying?
I can imagine one: just quickly check an idea or snippet without wanting to save it persistently.
Well
a) I may want to edit a file. Then, after running LP. I'm not happy with the result, so I want to revert to the original. I need to press CTRL-Z till the beginning of the editing!
b) I use LP with LyX. LyX run LP on the selected .ly files in a folder. The result is inserted in my document. No extra .ps or .pdf file is produced by LyX in my working dir (just in hi temp dir), which results in being very light (just .ly files!) If I edit them with LPTand I want to preview them, it will leave unwanted (relatively) big .pdf and .ps files. So I have to manually delete them if I want my folder to be light and easily portable.
Not a very important feature, but take it in account for next releases.
regards!
Then I think it should be a separate way of running Lily, a command for running on a temporary copy.
I change the summary, as for unsaved files, compiling will be possible. But for already saved files a new command will be created.