RE: bug report on 2.15.2 Mac OS X Intel version

[James Lowe]

Henk

____________________________________
From: Henk Verhaar address@hidden on behalf of Henk Verhaar address@hidden
Sent: 21 June 2011 11:25
To: James Lowe
Subject: Re: bug report on 2.15.2 Mac OS X Intel version

Yeah, done that - in fact it appears that the file was saved with the correct 
name, and the correct modification time, but without retaining any of the 
changes (I used a previous .ly file to adapt - this is what I normally do when 
creating .ly files, so that I do not have to manually enter a number of 
standard 'entries'. I could alternatively use a template, but in that case I'd 
have to update the template explicitly for each Lilypond update, or change in 
my preferred standard approach; in this way, I always have my most recent 
adaptations in my 'running' template...).

So what I did is, I copied an existing .ly file in the Finder and renamed it to 
its intended new name, ran the syntax updater, updated some fluff (some 
%obsolete marks introduced by the syntax updater), renamed the variables (name, 
composer, arranger, etc., cut out the previous music definition in the default 
\part {} (I use a \part {} construct standard), introduced a \transpose {} 
construct in my \score {} block, and entered the new music. Ran the 'Run' 
command a number of times until the part was ready and then printed it (I still 
have the finalized PDF file...), then closed Lilypond. When reopening the .ly 
file, the old content (albeit with the syntax updater fluff in there) was still 
there, and no sign of my edits. I may have done something wrong myself - I 
didn't document any of this, since this is my normal MO, but as said, it didn't 
quite result in what I expected...

On 21 jun 2011, at 12:13, James Lowe wrote:

> Henk,
>
> ________________________________________
> From: address@hidden address@hidden on behalf of Henk Verhaar address@hidden
> Sent: 21 June 2011 10:40
> To: address@hidden
> Subject: bug report on 2.15.2 Mac OS X Intel version
>
> Not a notation bug, but an I/O issue (possibly).
> This morning I installed 2.15.2 and successfully created a
> horn part for an adaptation of Fanfare for the Common Man
> (I was given F horn parts and needed them in
> E-flat, so I used the auto-transpose feature of Lilypond to
> create an Eb part. All worked fine, and I must
> have saved the source file a number of times during this
> process, since I know I created intermediate PDFs
> to check progress, and I have a PDF of the final score page
> that I will use. However, It appears that
> Lilypond has somehow removed my source file, or hid it,
> or saved it somewhere else, since I can no longer
> find the correct source file.
>
> I'll be reverting to 2.14 in the meantime...
>
> Cheers
>
> Henk
>
> --------------------------------------
>
> MacOSX has a basic search feature built into the finder, if you simply click 
> on a folder or the HD to open a window in the finder there are some search 
> filters in the left hand window 'SEARCH FOR'... Today, Yesterday, Past week.
>
> Can you use one of these to see if it has saved it in another place?
>
> I've been using 2.15.2 on MacosX and not had any problems like this.
>
> James

-------

Don't forget to cc the list so others can see (and help hopefully).

I've just done a simple test of copying/saving as an old file I did in 2.13 and 
making some trivial edits (delete some \header and \paper) etc and then keep 
compiling (edit, cmd-s, cmd-r, edit, cmd-s, cmd-r etc) I didn't lose the file.

So unless you can give me something that you might think is key then I'm, not 
sure what else to do to test to help troubleshoot.

:/

Can I just confirm that you were using the built in editor that comes with the 
mac version (as opposed to your own editor and the cli)?

James