On 2/17/2018 8:43 PM, Andrew Bernard wrote:
Hi Ben,
But then he is just writing a named file to the SSD, with the same
(non) issues, so this is not any different,
Using Frescobaldi is not a danger to SSD's or other life forms (as far
as we know...).
Andrew
Well no, if he saves the default directory preferences in Frescobaldi to
a non-SSD drive (i.e. a secondary drive) it's fine is what I meant.
I attached screenshots showing the setting but I guess if he only has
*one *drive in the system, then sure. Why not :) I guess so!
Either way, it's certainly a non-issue as far as SSD lifespan goes imo.
I agree.
On 18 February 2018 at 08:49, Ben <soundsfromso...@gmail.com
<mailto:soundsfromso...@gmail.com>> wrote:
Again, Frescobaldi does not save temporary files at all, unless
the file you're inputting and compiling has not been saved *once*.
So, as long as you open Frescobaldi and *save *the new document
with a filename, there won't be any 'temp files' to worry about.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
