Re: editor-lilypond quick parse

Hi could you send an example of how to do this? thanks Aaron --- Bertalan Fodor <[EMAIL PROTECTED]> wrote: > > > > > this functionality is already present. Just set > the > > toplevel-{music,book,text,score}-handler to > nop-functions. > > > Well, I see I must be more exact. I need a way to > f

Re: editor-lilypond quick parse

We could make the process much faster, if we could skip FontConfig initalization. What Han-Wen proposed was to write something like: #(set! toplevel-score-handler (lambda p 0)) That way lilypond will only parse. Its backdraw is that it won't find many typical typing errors (like unclosed beam

Re: editor-lilypond quick parse

> this functionality is already present. Just set the > toplevel-{music,book,text,score}-handler to > nop-functions. I don't understand. What does this do? and where and how exactly do I set this? Thanks Aaron __ Do You Yahoo!? Tired of spam? Y

Re: editor-lilypond quick parse

> > this functionality is already present. Just set the > toplevel-{music,book,text,score}-handler to nop-functions. > Well, I see I must be more exact. I need a way to find not-layout-related problems. So bar check fails, clashing voices, unfinished beams also should count. As Erik pointed out, l

Re: editor-lilypond quick parse

Bertalan Fodor wrote: One good thing would be if the parser were separated: if I call 'lilypond --parse-only', it writes the parsing errors to the standard output. Then it could be used to parse in the editor after some idle time, underlining errors and warnings. this functionality is already

Re: editor-lilypond quick parse

One good thing would be if the parser were separated: if I call 'lilypond --parse-only', it writes the parsing errors to the standard output. Then it could be used to parse in the editor after some idle time, underlining errors and warnings. Bert >The problem is that lily is too slow, and that th

Re: editor-lilypond quick parse

On Tuesday 23 August 2005 10.08, Bertalan Fodor wrote: > One good thing would be if the parser were separated: if I call > 'lilypond --parse-only', it writes the parsing errors to the standard > output. Then it could be used to parse in the editor after some idle > time, underlining errors and warn

Re: editor-lilypond quick parse

On Tuesday 23 August 2005 05.41, Aaron Mehl wrote: > Hi again, > > The problem is that I am not entering new music but > correcting existing notation, so that there are > already 50 measures written and I just corrected > measure 4. > but maybe it will help, I will give it a try I guess > if I jus

Re: editor-lilypond quick parse

Hi again, The problem is that I am not entering new music but correcting existing notation, so that there are already 50 measures written and I just corrected measure 4. but maybe it will help, I will give it a try I guess if I just pretend that there is no music after measure 5 whats the differ

Re: editor-lilypond quick parse

On Monday 22 August 2005 23.47, Aaron Mehl wrote: > Hi all, > > Is there a way to not have to reparse a file each time > I want to view changes? > > Something where only the newest changes are parsed or > the pdf is updated in almost realtime? > > I am using vim. If you're using 2.7, there is a co

editor-lilypond quick parse

Hi all, Is there a way to not have to reparse a file each time I want to view changes? Something where only the newest changes are parsed or the pdf is updated in almost realtime? I am using vim. Thanks Aaron Start your day