[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Files not saved before printng

From: Federico Bruni
Subject: Re: Files not saved before printng
Date: Sat, 11 Jul 2020 11:10:55 +0200

This is not a LilyPond bug.
If Frescobaldi doesn't warn you before closing an unsaved file, then this is a Frescobaldi bug. But I can't reproduce it on Linux. Are you really sure that no warning appears? It would be a serious bug.

On Fri, 10 Jul, 2020 at 14:18, JH Austin <jaustin-rr@nc.rr.com> wrote:
I'm not sure you would call this is bug or just a user error,
but I have lost a couple files recently.
Using Frescobaldi and Lilypond, after composing and printing a file correctly,
the saved file is still back-level to the printed copy.

Here you say: printed copy is up-to-date, file is out-of-date. It seems impossible. I wouldn't say "back-level". I would just say they are different.
What you write after seems to contradict this statement.

Having a "good" printout and thinking I was finished, I exited the program, apparently without saving, and all my revisions disappeared.

Stupid me! Guess I've gotten so used to modern programs that do auto-save that I've developed sloppy habits.

But it would be helpful to warn the user before printing if the file has not been saved.

This makes more sense maybe, if I understand correctly.
But I won't try to interpret your words. Please try to reformulate better what happened.

I have the feeling that setting the preference "save file before compiling" would solve your issues. I think this should be the default, as new users are often confused about this Frescobaldi behaviour.

I'm running:
Frescobaldi 3.1.2
Lilypond 2.20.0-1
Mac OS 10.13.4 High Sierra

reply via email to

[Prev in Thread] Current Thread [Next in Thread]