bug-lilypond
[Top][All Lists]
Advanced

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

Re: clean numbered backups with convert-ly


From: David Kastrup
Subject: Re: clean numbered backups with convert-ly
Date: Thu, 24 Oct 2013 10:54:00 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Eluze <address@hidden> writes:

> David Kastrup wrote
>> Eluze &lt;
>
>> eluzew@
>
>> &gt; writes:
>> 
>>> David Kastrup wrote
>> 
>> And then I would be afraid that it would do something besides cleaning
>> up the backups, some conversion or so.  When using rm *.ly.~* I know
>> exactly what will happen.
>
> and this would remove files marked .~25~toBeKept

Yes.  Emacs uses this kind of file name when checking out files from a
version control system corresponding to a different than the current
commit.  If you name files like that, they are expected to be treated
like backup files by file managers.

>> [...]
>> With regard to the
>> documentation: that would make sense.  I did not object to that, merely
>> explained why nobody might have thought of mentioning it before.  I'd
>> have said that one should not just restrict this to convert-ly, but at
>> least lilypond and lilypond-book have so few parameterless options that
>> it seems hardly worth the trouble to mention that possibility with them.
>
> maybe just adding an example with recommended parameters would help make
> convert-ly more popular?
>
> convert-ly -ec myFile.ly     updates myFile.ly to the current version and
> makes a simple backup in the file myFile.ly~
> or 
> convert-ly -ecb myFile.ly   updates myFile.ly to the current version and
> makes a numbered backup myFile.ly~number~
>
>
> btw - why is -c - now the default - not mentioned in the doc? it is when the
> help text is displayed:
>
>
> -c, --current-version
>                      force updating \version number to 2.17.29

I have not bothered writing documentation for it when I last dealt with
convert-ly since the code looked quite suspicious.  I could not deduce
the exact behavior this was intended to provide.

-- 
David Kastrup




reply via email to

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