Re: tie attached on left side

[Arvid Grøtting]

Laura Conrad  laymusic.org> writes:

> There's a more important problem (to me) that appeared in 2.9.23, so
> I'm not updating until somebody fixes or finds a good workaround for
> the lilypond-book staff alignment problem.

Mine's stopped working, then?  (I haven't checked.)

Oh, well; it was an ugly hack.

-- 

Arvid






___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Windows Lilypond 2.11.1

[Trent Johnston]

Hi Everyone,

The latest Lilypond 2.11.1 on my work laptop and home computer is extremely 
slow.. to the point of going in what seems to be an infinite loop.

I've monitored the process with task manager and noticed that Lilypond 
(gauging from the memory usage of this version and the previous version 
2.11.0-1) that lilypond seems to continuly runs itself over and over again. 
The memory useage peaks at 240, 000K for a score then declines very slowly 
back down to around 6,000K only to start up again moving back up to 
240,000K. I noticed that lilypond did this 10 times before I stopped the 
process (I also noticed that CPU percentage never got above 20). I 
uninstalled 2.11.1 and reinstalled 2.11.0-1 and ran the file again .. no 
problems Lilypond ran the memory usage peaked around 260,000K this time (all 
while CPU percentage was at about 49 for most of the time) and memory useage 
decline until the application terminated after producing the PDF output at 
about 3 minutes to the well over 15 minutes on 2.11.1 before I stopped it.

Has anyone else had similar problems?

Trent 



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: tie attached on left side

[Graham Percival]

Arvid Grøtting wrote:

Laura Conrad  laymusic.org> writes:


There's a more important problem (to me) that appeared in 2.9.23, so
I'm not updating until somebody fixes or finds a good workaround for
the lilypond-book staff alignment problem.


Mine's stopped working, then?  (I haven't checked.)

Oh, well; it was an ugly hack.


Lilypond now produces binary eps files.  See
http://code.google.com/p/lilypond/issues/detail?id=157

Cheers,
- Graham


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: tie attached on left side

[Arvid Grøtting]

Graham Percival  gmail.com> writes:

> Lilypond now produces binary eps files.  See
> http://code.google.com/p/lilypond/issues/detail?id=157

I get errors from lilypond-book now, possibly because I haven't updated the
included files, but the BoundingBox is in the text-format header.  The ugly sed
trick itself still seems to work.

-- 

Arvid






___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Church music

[Jean-marc LEGRAND]

Hi !

Could you send a png of your score, please ? I don't really understand the 
precise question ?

As I'm french, could you explain what episems are ?

Regards

JMarc



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: tie attached on left side

[Laura Conrad]

> "Arvid" == Arvid Grøtting <[EMAIL PROTECTED]> writes:

Arvid> Graham Percival  gmail.com> writes:
>> Lilypond now produces binary eps files.  See
>> http://code.google.com/p/lilypond/issues/detail?id=157

Arvid> I get errors from lilypond-book now, possibly because I
Arvid> haven't updated the included files, but the BoundingBox is
Arvid> in the text-format header.  The ugly sed trick itself still
Arvid> seems to work.

Thanks, you're right.  I don't know what my problem was, but I hit it
when I was modifying my script to do a 'grep -l' to avoid having
to do the sed on eps files that have already been modified, which was
taking too long on a big project.  But my current script works on both
2.10.1 and 2.11.1.

-- 
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097  fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: which language for programming

[Jean-marc LEGRAND]

For the frenchies who'd like to learn python, I must say that Gérard Swinnen's 
"Apprendre à
programmer avec Python", is really amazing (I understand everything ). I 
found it on
developpez.com.

Regards !

Jmarc



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond and editors

[Andreas v. Heydwolff]

confrey wrote:

Hi everybody,
I know some text editors have a support for lilypond; I'd like to know
what's a fine editor for lilypond, and if it is possible to customize
gedit (sintax highlighting and statement recognition adn completation).
bye



confrey



kate with colored syntax (downloadable somewhere), utf-encoding, command
line window for compiling, code snippet and session saving. "Rocks."

Andreas v.H.

(sorry for PM)


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis [was: Re: Tutorial]

[Valentin Villenave]

2006/12/6, Bertalan Fodor <[EMAIL PROTECTED]>:


It seems that you don't use LilyPondTool. If you used it, you would have
a full-text search of LilyPond doc. See the screenshot at
http://www.organum.hu/87.0.html



As a matter of fact, I do use LilypondTool. But I just did'nt remember
the doc was included. Thanks a lot, this will be extremely valuable to
me I guess...

2006/12/6, Graham Percival <[EMAIL PROTECTED]>:


2)  What info was so hard to find?  Can you think of any way to improve
the lilypond docs?  (missing terms in the index, perhaps?)


Well, my problems mostly come from the fact I don't always know the
right English word for what I'm looking for... But let me try to sum
up a few  things I said to myself once :
-it's a pity the LSR is a bit poor
-we're missing some recent examples ; I often look for, say,
orchestral scores on Mutopia or Lilypond pages but I'm always very
disappointed these are mostly written with 2.4 or 2.6 (and convert-ly
doesn't always work very well you know, especially with 2.10...)
-a little box with a simple "search" button would be welcome on
Lilypond.org, I really can tell you. Maybe it isn't the point to have
some of those roaring websites, with complicated CMS, stylesheets,
interface etc., but just a simple integrated search function ; is it
possible to think about it ?

You see, I understand LilyPond docs are very well organized. But we
average users (and newbies) are not _that_ rational. Sometimes,
navigating through tutorial, documentation, sections, sub-sections and
so on can be longer and more difficult (no matter how "logical" it can
be)  than just typing a keyword and letting the computer find it for
you.

And once again, (and since I've learned there is actually some
LilyPond-oriented MediaWiki extension), I can't help dreaming of an
entire Wikipedia-style Lily doc...

But thank you all for having taken a few seconds to answer me.

Thanks for the Todo-list Graham. I'll try to give it a look though I'm
not that experienced...

Regards,
V.Villenave


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Globally removing string number engraver

[Rick Hansen (aka RickH)]

Notice in the following example (which will run as-is) that I am explicitely
removing the string number engraver.  Yet, alas, the string numbers remain
on the staff portion.

How can I globally remove the string numbers from the standard notation
staff, and still reuse the same music on the Fretboards staff?  (without
having to modify the music itself).

I thought removing the string number engraver should do it.  Is there maybe
a transparent property for string numbers?

Thanks
Rick


 EXAMPLE BEGIN


\version "2.11.1"
\include "english.ly"

varFretBoardsCheatSheet = {
   s4
   \transpose c ef \relative {  }
   \transpose c c \relative {  }
}

\header {
tagline = " "
}

\score {

   <<

   \new Staff \with {
\override Stem #'transparent = ##t
   }
   {
#(set-accidental-style 'forget)
\key c \major
\varFretBoardsCheatSheet
   }

   \new FretBoards { \transpose c c, {
\varFretBoardsCheatSheet
}
   }

   >>  % end music expression

   \layout {
 ragged-right = ##t
 ragged-last = ##t
 ragged-bottom = ##t
 ragged-last-bottom = ##t
 indent = 0.0\in
 \context { \Score
\remove Bar_number_engraver
 }
 \context { \Staff
\remove Clef_engraver
\remove Time_signature_engraver
\remove String_number_engraver
 }
 \context { \FretBoards
\override FretBoard #'number-type = #'arabic
 }
   } % end layout

} % end score

\paper {
}


 EXAMPLE END


-- 
View this message in context: 
http://www.nabble.com/Globally-removing-string-number-engraver-tf2776391.html#a7745355
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis [was: Re: Tutorial]

[Mats Bengtsson]

Quoting Valentin Villenave <[EMAIL PROTECTED]>:


Well, my problems mostly come from the fact I don't always know the
right English word for what I'm looking for...


I hope you have seen the Music glossary, included in the LilyPond
documentation.


-a little box with a simple "search" button would be welcome on
Lilypond.org, I really can tell you. Maybe it isn't the point to have
some of those roaring websites, with complicated CMS, stylesheets,
interface etc., but just a simple integrated search function ; is it
possible to think about it ?


There is a search function, at the bottom of www.lilypond.org, even 
though one of the problems with it is that it often lists links to old 
versions of the manual first.



...
You see, I understand LilyPond docs are very well organized. But we
average users (and newbies) are not _that_ rational. Sometimes,
navigating through tutorial, documentation, sections, sub-sections and
so on can be longer and more difficult (no matter how "logical" it can
be)  than just typing a keyword and letting the computer find it for
you.


I also hope you have found the index of the manual (it seems that many 
people miss it (partly since it's called "LilyPond index" for

silly technical reasons).


  /Mats




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Globally removing string number engraver

[Mats Bengtsson]

If you follow the link to "StringNumber" at the bottom of the page on 
"String number indications" in the manual, you will find out that 
"StringNumber objects are created by: New_fingering_engraver"

and if you keep clicking to find out in which context this engraver
lives by default, you'll find out that it's in the Voice context.
I think that's all information you need.

Don't ask me what the String_number_engraver does, though.

 /Mats

Quoting "Rick Hansen (aka RickH)" <[EMAIL PROTECTED]>:



Notice in the following example (which will run as-is) that I am explicitely
removing the string number engraver.  Yet, alas, the string numbers remain
on the staff portion.

How can I globally remove the string numbers from the standard notation
staff, and still reuse the same music on the Fretboards staff?  (without
having to modify the music itself).

I thought removing the string number engraver should do it.  Is there maybe
a transparent property for string numbers?

Thanks
Rick



EXAMPLE BEGIN



\version "2.11.1"
\include "english.ly"

varFretBoardsCheatSheet = {
  s4
  \transpose c ef \relative {  }
  \transpose c c \relative {  }
}

\header {
tagline = " "
}

\score {

  <<

  \new Staff \with {
   \override Stem #'transparent = ##t
  }
  {
   #(set-accidental-style 'forget)
   \key c \major
   \varFretBoardsCheatSheet
  }

  \new FretBoards { \transpose c c, {
   \varFretBoardsCheatSheet
   }
  }

  >>  % end music expression

  \layout {
ragged-right = ##t
ragged-last = ##t
ragged-bottom = ##t
ragged-last-bottom = ##t
indent = 0.0\in
\context { \Score
   \remove Bar_number_engraver
}
\context { \Staff
   \remove Clef_engraver
   \remove Time_signature_engraver
   \remove String_number_engraver
}
\context { \FretBoards
   \override FretBoard #'number-type = #'arabic
}
  } % end layout

} % end score

\paper {
}



EXAMPLE END



--
View this message in context: 
http://www.nabble.com/Globally-removing-string-number-engraver-tf2776391.html#a7745355

Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user







___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis [was: Re: Tutorial]

[Valentin Villenave]

2006/12/7, Mats Bengtsson <[EMAIL PROTECTED]>:


There is a search function, at the bottom of www.lilypond.org, even
though one of the problems with it is that it often lists links to old
versions of the manual first.


Hmmm... I have indeed _never_ noticed it, and thank you very very much
for having pointed it. The fact is, I have bookmarked the page
http://lilypond.org/web/documentation and
http://lilypond.org/doc/v2.10/Documentation/user/lilypond/index.html
but never, never the home page ; moreover, if I ever came on
lilypond.org home page, I've been used to immediately click on the
"Documentation" link on top. Therefore I did not notice it at all.

Maybe it would be wise (for dummies like me, if there are any others,
who knows) to add a similar search function on
http://lilypond.org/web/documentation and maybe, one "per-version" (no
silly joke) search on http://lilypond.org/doc/v2.10/Documentation/ and
so on.



> ...
I also hope you have found the index of the manual (it seems that many
people miss it (partly since it's called "LilyPond index" for
silly technical reasons).



Well I guess I was part of those people until now... My bad.
Are you talking about
http://lilypond.org/doc/v2.10/Documentation/user/lilypond-internals/Indexes.html#Indexes
? Here again, maybe adding a link on
http://lilypond.org/doc/v2.10/Documentation/ would be appropriate...

Thank you Mats.

V.Villenave.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond and editors

[Andreas v. Heydwolff]

confrey wrote:

Hi everybody,
I know some text editors have a support for lilypond; I'd like to know
what's a fine editor for lilypond, and if it is possible to customize
gedit (sintax highlighting and statement recognition adn completation).
bye



confrey



kate with colored syntax (downloadable somewhere), utf-encoding, command
line window for compiling, code snippet and session saving. "Rocks."

Andreas v.H.

(sorry for PM)



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Globally removing string number engraver

[Rick Hansen (aka RickH)]

Mats Bengtsson-4 wrote:
> 
> If you follow the link to "StringNumber" at the bottom of the page on 
> "String number indications" in the manual, you will find out that 
> "StringNumber objects are created by: New_fingering_engraver"
> and if you keep clicking to find out in which context this engraver
> lives by default, you'll find out that it's in the Voice context.
> I think that's all information you need.
> 
> Don't ask me what the String_number_engraver does, though.
> 
>   /Mats
> 
> Quoting "Rick Hansen (aka RickH)" <[EMAIL PROTECTED]>:
> 
>>
>> Notice in the following example (which will run as-is) that I am
>> explicitely
>> removing the string number engraver.  Yet, alas, the string numbers
>> remain
>> on the staff portion.
>>
>> How can I globally remove the string numbers from the standard notation
>> staff, and still reuse the same music on the Fretboards staff?  (without
>> having to modify the music itself).
>>
>> I thought removing the string number engraver should do it.  Is there
>> maybe
>> a transparent property for string numbers?
>>
>> Thanks
>> Rick
>>
>>
>> EXAMPLE BEGIN
>>
>>
>> \version "2.11.1"
>> \include "english.ly"
>>
>> varFretBoardsCheatSheet = {
>>   s4
>>   \transpose c ef \relative {  }
>>   \transpose c c \relative {  }
>> }
>>
>> \header {
>>  tagline = " "
>> }
>>
>> \score {
>>
>>   <<
>>
>>   \new Staff \with {
>>\override Stem #'transparent = ##t
>>   }
>>   {
>>#(set-accidental-style 'forget)
>>\key c \major
>>\varFretBoardsCheatSheet
>>   }
>>
>>   \new FretBoards { \transpose c c, {
>>\varFretBoardsCheatSheet
>>}
>>   }
>>
>>   >>  % end music expression
>>
>>   \layout {
>> ragged-right = ##t
>> ragged-last = ##t
>> ragged-bottom = ##t
>> ragged-last-bottom = ##t
>> indent = 0.0\in
>> \context { \Score
>>\remove Bar_number_engraver
>> }
>> \context { \Staff
>>\remove Clef_engraver
>>\remove Time_signature_engraver
>>\remove String_number_engraver
>> }
>> \context { \FretBoards
>>\override FretBoard #'number-type = #'arabic
>> }
>>   } % end layout
>>
>> } % end score
>>
>> \paper {
>> }
>>
>>
>> EXAMPLE END
>>
>>
>> --
>> View this message in context: 
>> http://www.nabble.com/Globally-removing-string-number-engraver-tf2776391.html#a7745355
>> Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
>>
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> http://lists.gnu.org/mailman/listinfo/lilypond-user
>>
> 
> 
> 
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 


Thanks Mats,

Adding this to the \layout block removes the string numbers:

 \context { \Voice
\remove New_fingering_engraver
 }

"String_number_engraver" is apparently part of TabStaff.

Apparently it was easy for someone to keep string numbers, fretting hand,
and stroke hand numbers all in the same engraver called
"New_fingering_engraver".  But globally removing string numbers also
clobbers the finger numbers.  That's ok for my case but maybe in the future
3 different tranparent properties could be added to the
New_fingering_engraver to let you turn on/off fret hand, stroke hand, and
string numbers independently.

thanks again


-- 
View this message in context: 
http://www.nabble.com/Globally-removing-string-number-engraver-tf2776391.html#a7746874
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis [was: Re: Tutorial]

[Mats Bengtsson]

Quoting Valentin Villenave <[EMAIL PROTECTED]>:


I also hope you have found the index of the manual (it seems that many
people miss it (partly since it's called "LilyPond index" for
silly technical reasons).



Well I guess I was part of those people until now... My bad.
Are you talking about
http://lilypond.org/doc/v2.10/Documentation/user/lilypond-internals/Indexes.html#Indexes


No! Click on Documentation -> User Manual -> LilyPond Index

  /Mats




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond and editors

[Frédéric Chiasson]

Hi everyone,

On the same subject, I would like to propose an improvement for the Lilypond
editor on Mac OS (mine is 10.4). It would be really nice if we could point
and click on an error message and the code creating the error would be
highlighted. Or, an easier thing to program, a line and character counter in
the editor would be great, since the error messages give the line number
where the bug is. It would be a great improvement.

By the way, is there any editor having LilyPond tool other than jEdit?

Thanks,

Frédéric Chiasson


2006/12/7, Andreas v. Heydwolff <[EMAIL PROTECTED]>:


confrey wrote:
> Hi everybody,
> I know some text editors have a support for lilypond; I'd like to know
> what's a fine editor for lilypond, and if it is possible to customize
> gedit (sintax highlighting and statement recognition adn completation).
> bye

> confrey


kate with colored syntax (downloadable somewhere), utf-encoding, command
line window for compiling, code snippet and session saving. "Rocks."

Andreas v.H.

(sorry for PM)



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

OS X question about Apple's Preview

[Trevor Bača]

Hi,

Not a direct Lily question, but useful nonetheless:

Any OS X folks know how to tell Apple's Preview application -- from
the commandline -- to close foo.pdf (but leave other pdfs open, ie,
without actually killing the Preview process)?


--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis [was: Re: Tutorial]

[John Mandereau]

Mats Bengtsson wrote:
> Quoting Valentin Villenave <[EMAIL PROTECTED]>:
> 
> > Well, my problems mostly come from the fact I don't always know the
> > right English word for what I'm looking for...
> 
> I hope you have seen the Music glossary, included in the LilyPond
> documentation.

Frédéric Chiasson has just made a glossary (with no definitions, only
direct equivalent translations) for the French translators; it's
available in the archives of the lilypond-user-fr list.

Btw, there are also the full table of contents of the user manual, and
the one-big-page flavours of the user manual and the program reference.
You can search them with the "Find" or "Search" feature of your web
browser.



> I also hope you have found the index of the manual (it seems that many 
> people miss it (partly since it's called "LilyPond index" for
> silly technical reasons).

Maybe it could be renamed to "Full index"?


-- 
John Mandereau <[EMAIL PROTECTED]>



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Lilypond and editors

[César Penagos]

I run lilypond under windows Xp,  and actually I´m using a very naice 
editor (notepad II)  It works excellent, whit all the features needed 
for lilypond.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis [was: Re: Tutorial]

[John Mandereau]

[CCing back to the list...]
Christophe Dang Ngoc Chan wrote:
> Le 5 déc. 06 à 23:29, John Mandereau a écrit :
> > It's easy to start a new wiki, a new documentation, a new whatever,  
> > but
> > it's much harder to develop it on a long timescale.
> >
> > Before reinventing the wheel, [...]
> 
> I have a different point of view. You cannot write something that  
> fits everybody, some people understand things explained in a way,  
> some others in another way.
> 
> There multiplicity of the handbooks is considered a a good thing for  
> schoolbooks, and you find several different manuals on a lot of  
> topics (history, programming, foreign languages etc.), and you can / 
> choose/ the one that fits the way you understand things. I do not  
> think this is reinventing the wheel.

Agreed. I've really had a totalitarian point of view. To be more
positive, I'd like all these "tutorial introductions" to LilyPond to be
referenced in the "Resources links" on lilypondwiki.tuxfamily.org, and
that some ideas from these pages could be reused to improve the official
tutorial. That's more easy to say than to do, of course.

Reinventing the wheel doesn't really apply to tuorials, because it's
pedagogical documentation, and there can be a lot of different
pedagogical points of view. My criticism about "reinventing the wheel"
should rather have applied to the reference manual and the ly snippets:
imho it's more important to try to centralize them than the tutorials.

Best regards,
-- 
John Mandereau <[EMAIL PROTECTED]>



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond and editors

[Thomas Scharkowski]

Just curious:
what's wrong with jEdit?
Thomas

> Hi everyone,
>
> On the same subject, I would like to propose an improvement for the Lilypond
> editor on Mac OS (mine is 10.4). It would be really nice if we could point
> and click on an error message and the code creating the error would be
> highlighted. Or, an easier thing to program, a line and character counter in
> the editor would be great, since the error messages give the line number
> where the bug is. It would be a great improvement.
>
> By the way, is there any editor having LilyPond tool other than jEdit?
>
> Thanks,
>
> Frédéric Chiasson
>
>
> 2006/12/7, Andreas v. Heydwolff <[EMAIL PROTECTED]>:
> >
> > confrey wrote:
> > > Hi everybody,
> > > I know some text editors have a support for lilypond; I'd like to know
> > > what's a fine editor for lilypond, and if it is possible to customize
> > > gedit (sintax highlighting and statement recognition adn completation).
> > > bye
> >
> > > confrey
> >
> >
> > kate with colored syntax (downloadable somewhere), utf-encoding, command
> > line window for compiling, code snippet and session saving. "Rocks."
> >
> > Andreas v.H.
> >
> > (sorry for PM)
> >
> >
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > http://lists.gnu.org/mailman/listinfo/lilypond-user
> >
>




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: OS X question about Apple's Preview

[Trevor Bača]

On 12/7/06, Trevor Bača <[EMAIL PROTECTED]> wrote:

Hi,

Not a direct Lily question, but useful nonetheless:

Any OS X folks know how to tell Apple's Preview application -- from
the commandline -- to close foo.pdf (but leave other pdfs open, ie,
without actually killing the Preview process)?


Christian was kind enough to provide a pointer an article that leads here.

1. go to http://vocaro.com/trevor/software/applescript/ (the
maintainer of the page is some other Trevor, not me)

2. scroll down and download the "Reload Preview Document" applescript

3. unzip the resulting applescript and put somewhere on the filesystem
such that PATH knows about the script

4. the usage is then

 osascript "Reload Preview Document.scpt" foo.pdf


--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis [was: Re: Tutorial]

[John Mandereau]

Valentin Villenave wrote:
> 2006/12/5, John Mandereau <[EMAIL PROTECTED]>:
> >
> > Before reinventing the wheel, we should first look for what already
> > exists (or has existed).
> 
> I don't think Christophe Dang Ngoc Chan is pretending to reinvent the
> wheel (and neither am I, by the way). There is no need to blame
> newly-arrived users who want to help, no matter how unconvenient their
> ideas can be.

Newly-arrived users sometimes have great ideas. I have



> > 2) Johannes Schindelin has already developped a Mediawiki extension that
> > can run LilyPond.
> >
> 
> This is great. Looks like we get one more reason to use a wiki...

Yes, if you can find
> > As Graham and others have already pointed out, it'd be very cumbersome
> > for the user to look for documentation at a dozen of places. Computer
> > music engraving, and thus LilyPond, are so specialized that cluttered
> > and concurrent sources of informations would really be a pain.
> > IMHO everyone should think twice about it before creating a new source
> > of information.
> >
> 
> The fact is, there's obviously something wrong with the way Lilypond
> documentation is given. A dozen of places, indeed :  I use almost
> everyday : Lilypond snippet repository, Lily's official doc (not to
> mention that sometimes you need to switch to v8 or v9 doc to find
> something you need, then back again to v10 and so on), your site
> john.mandereau.free.fr to figure out what this word mean in French,
> etc., etc.

The French translation will be available soon on lilypond.org.
Graham has a plan to centralize snippets (I mean you could find almost
all code snippets in one place), but I don't know the current state of
this.


> IMHO, the most obvious lack isn't a lack of content, but a lack of
> intern links and "interface", so to say. Which means, and that's good
> news, that maybe the problem isn't so deep and so hard to correct. But
> maybe I'm reinventing the wheel here... :)

No, you're not. Organising the contents is certainly more difficult than
writing bits of documentation.


> The point is, precisely, all of us should not attempt to create a new
> source of information at all, but try to make existing Lilypond
> Documentation as easy and user- or contributer-friendly as, say,
> Wikipedia or anything else.
> 
> That said, I'm glad it already exists (means the idea was'nt _that_
> bad), though it is unfortunately a bit hard to find. I can't
> understand why it hasn't been a success. But maybe it would be worth
> trying to to put the footer links again. Can this be done easily, or
> does it means spending hours page-per-page ?

Putting the footer links again only require one-line fix in a build
script and a small setup in a wiki. If the developers agree, and if you
promise to write comments ;-), I may set it up on the tuxfamily.org
wiki.


> And one last thing : both Christophe and I, I guess, and many others
> (that is, as far as they know there _is_ a wiki without having to read
> the entire mailing list archive) would be happy to join you and
> contribute to the existing wiki -unless you believe it is dead.

No, it isn't dead. It's just sleeping. You are of course welcome to
contribute! For example, you could add links to tutorial stuff you cand
find on the Web to the "Tutorial and examples" page
http://lilypondwiki.tuxfamily.org/index.php?title=Tutorials_and_examples

There is also a small to-do list at "Community portal", and the
guidelines on
http://lilypondwiki.tuxfamily.org/index.php?title=LilypondWiki:Guidelines

Good luck ;-)

-- 
John Mandereau <[EMAIL PROTECTED]>



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: OS X question about Apple's Preview

[Arjan Bos]

On 7 dec 2006, at 21:33, Trevor Bača wrote:


Hi,

Not a direct Lily question, but useful nonetheless:

Any OS X folks know how to tell Apple's Preview application -- from
the commandline -- to close foo.pdf (but leave other pdfs open, ie,
without actually killing the Preview process)?


The most obvious way would be to use Applescript, unfortunately,  
Applescript isn't supported by Preview.app. But macworld.com has the  
solution: 


Here they turn on Applescript from the command line with:
defaults write /Applications/Preview.app/Contents/Info  
NSAppleScriptEnabled -bool YES


And then you can close a window with:

tell application "Preview"
close window 1
end tell

I have not yet used it, but presumably, every OS update that also  
updates Preview.app will override this setting back to the default.


Some quick experimenting results in:

tell application "Preview"
repeat with i from 1 to number of windows
set current_window to item i of windows
set current_name to name of the document of the current_window
if current_name is "AdemVanEeuwigheid.pdf" then
close window i
exit repeat
end if
end repeat
end tell

Where AdemVanEeuwigheid.pdf is a pdf of a lilypond score.

Perhaps you can make this into a folder action that executes on the  
directory where your pdfs are created in?



HTH,
Arjan

---
They both savoured the strange warm glow of being much more ignorant  
than ordinary people, who were only ignorant of ordinary things.


-- Discworld scientists at work  (Terry Pratchett, Equal Rites)



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: OS X question about Apple's Preview

[Arjan Bos]

On 7 dec 2006, at 22:11, Trevor Bača wrote:


On 12/7/06, Trevor Bača <[EMAIL PROTECTED]> wrote:

Christian was kind enough to provide a pointer an article that  
leads here.


1. go to http://vocaro.com/trevor/software/applescript/ (the
maintainer of the page is some other Trevor, not me)

2. scroll down and download the "Reload Preview Document" applescript

3. unzip the resulting applescript and put somewhere on the filesystem
such that PATH knows about the script

4. the usage is then

 osascript "Reload Preview Document.scpt" foo.pdf



Which is of course much more useful than that hack I just sent  
you! :-) It should be the default for previewing documents.


Arjan

---
Ankh-Morpork had dallied with many forms of government and had ended  
up with that form of democracy known as One Man, One Vote. The  
Patrician was the Man; he had the Vote.


-- Discworld politics explained  (Terry Pratchett, Mort)



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond and editors

[Geoff Horton]

On 12/7/06, Thomas Scharkowski <[EMAIL PROTECTED]> wrote:

Just curious:
what's wrong with jEdit?
Thomas


Editors are one of those things that really depend on personal taste.
It may just be that I've been using emacs for too long, but jEdit
drove me nuts. Others have their favorite way of doing things, and
jEdit may or may not work well with that.

So what's wrong with jEdit? Nothing, if it fits the way you work.

Geoff


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis [was: Re: Tutorial]

[Graham Percival]

John Mandereau wrote:


Graham has a plan to centralize snippets (I mean you could find almost
all code snippets in one place), but I don't know the current state of
this.


Exactly the same as it was last August.
http://lists.gnu.org/archive/html/lilypond-devel/2006-08/msg00146.html


That said, I'm glad it already exists (means the idea was'nt _that_
bad), though it is unfortunately a bit hard to find. I can't
understand why it hasn't been a success. But maybe it would be worth
trying to to put the footer links again. Can this be done easily, or
does it means spending hours page-per-page ?


Putting the footer links again only require one-line fix in a build
script and a small setup in a wiki. If the developers agree,


I don't.  I'll play the evil totalitarian guy here.

Writing good documentation is hard.  I know that better than most: I've 
spent almost 1000 hours working on the current docs.  "Wiki" isn't a 
magic wand that you can wave and get good docs.  Documentation requires 
time and effort.


I have a challenge: before complaining about my anti-wiki position, 
spend five hours writing docs for the official docs.  It doesn't have to 
be all at once; spend half an hour one day, maybe an hour on the next, 
etc.  Send your doc changes to me according to this page:

http://lilypond.org/web/devel/participating/documentation-adding

If you want ideas on what to work on, I'm more than happy to discuss it 
with you.  (but the time spent on that discussion doesn't count towards 
those five hours)


This doesn't need to be original work; if you find some info in an email 
from lilypond-user that should be in the docs, by all means submit that.


- Graham Percival


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond and editors

[Bertalan Fodor]

Often one can gain productivity by fitting his way of work to the editor :-)

Bert


So what's wrong with jEdit? Nothing, if it fits the way you work.




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond and editors

[Geoff Horton]

Often one can gain productivity by fitting his way of work to the editor :-)

Bert


Sometimes, yes. Often ... I don't know about that, and I'm not really
a fan of the idea. Tools exist for me; I don't exist for tools.

I don't mean to discourage anyone from trying jEdit. I did. I prefer
something else. YMMV :)

Geoff


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond and editors

[Frédéric Chiasson]

Well, I never tried jEdit on Mac. But I tried it on PC and the LilypondTool
didn't work out and I had so many problems that I discarded it after a week.

Maybe I should give it a second shot. It migth work better on Mac OS.

Thanks for the comments,

Frédéric


2006/12/7, Bertalan Fodor <[EMAIL PROTECTED]>:


Often one can gain productivity by fitting his way of work to the editor
:-)

Bert

> So what's wrong with jEdit? Nothing, if it fits the way you work.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Globally removing string number engraver

[Mats Bengtsson]

Quoting "Rick Hansen (aka RickH)" <[EMAIL PROTECTED]>:

Thanks Mats,

Adding this to the \layout block removes the string numbers:

\context { \Voice
   \remove New_fingering_engraver
}

"String_number_engraver" is apparently part of TabStaff.

Apparently it was easy for someone to keep string numbers, fretting hand,
and stroke hand numbers all in the same engraver called
"New_fingering_engraver".  But globally removing string numbers also
clobbers the finger numbers.  That's ok for my case but maybe in the future
3 different tranparent properties could be added to the
New_fingering_engraver to let you turn on/off fret hand, stroke hand, and
string numbers independently.


Read in "Common Tweaks" on how to make things invisible. In this specific
case, you could use
\override StringNumber #'transparent = ##t

An alternative, if you don't want it to take any space at all, is to use
\override StringNumber #'stencil = ##f
(this isn't yet in the manual).

  /Mats




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond and editors

[Bertalan Fodor]

Should you have any problems I'm here to help ;-) Remember to look at 
http://lilypondtool.organum.hu


Bert

Frédéric Chiasson írta:
Well, I never tried jEdit on Mac. But I tried it on PC and the 
LilypondTool didn't work out and I had so many problems that I 
discarded it after a week.


Maybe I should give it a second shot. It migth work better on Mac OS.

Thanks for the comments,

Frédéric


2006/12/7, Bertalan Fodor <[EMAIL PROTECTED] 
>:


Often one can gain productivity by fitting his way of work to the
editor :-)

Bert

> So what's wrong with jEdit? Nothing, if it fits the way you work.



___
lilypond-user mailing list
lilypond-user@gnu.org 
http://lists.gnu.org/mailman/listinfo/lilypond-user






___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis

[Kevin Dalley]

The nice thing about a wiki is that I can spend 15 minutes improving
the one area which I now understand after spending an hour
researching.

Then, next month, I'll spend another 15 minutes.

Pages which are often references tend to get better quickly.

I probably won't spend 5 hours writing lilypond docs, but I might
spend 15 minutes a few times a year.

Graham Percival <[EMAIL PROTECTED]> writes:

> I have a challenge: before complaining about my anti-wiki position,
> spend five hours writing docs for the official docs.  It doesn't have
> to be all at once; spend half an hour one day, maybe an hour on the
> next, etc.  Send your doc changes to me according to this page:
> http://lilypond.org/web/devel/participating/documentation-adding
>
> If you want ideas on what to work on, I'm more than happy to discuss
> it with you.  (but the time spent on that discussion doesn't count
> towards those five hours)
>
> This doesn't need to be original work; if you find some info in an
> email from lilypond-user that should be in the docs, by all means
> submit that.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis [was: Re: Tutorial]

[John Mandereau]

Graham Percival wrote:
> John Mandereau wrote:
> > Putting the footer links again only require one-line fix in a build
> > script and a small setup in a wiki. If the developers agree,
> 
> I don't.  I'll play the evil totalitarian guy here.
> 
> Writing good documentation is hard.  I know that better than most: I've 
> spent almost 1000 hours working on the current docs.  "Wiki" isn't a 
> magic wand that you can wave and get good docs.  Documentation requires 
> time and effort.
> 
> I have a challenge: before complaining about my anti-wiki position, 
> spend five hours writing docs for the official docs.  It doesn't have to 
> be all at once; spend half an hour one day, maybe an hour on the next, 
> etc.  Send your doc changes to me according to this page:
> http://lilypond.org/web/devel/participating/documentation-adding

Your long experience with the docs may allow you to be more totalitarian
than me :-)

I'll soon have stuff to commit on the tutorial, when I've finished
hacking these buildscripts for the French tutorial release.

Cheers,
-- 
John Mandereau <[EMAIL PROTECTED]>



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis

[Graham Percival]

Kevin Dalley wrote:

The nice thing about a wiki is that I can spend 15 minutes improving
the one area which I now understand after spending an hour
researching.


The same applies to the main docs!  Spend 10 minutes making a good small 
lilypond example, spend five minutes writing two or three sentences 
explaining the example, then email it to me.


http://lilypond.org/web/devel/participating/documentation-adding

- Graham


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lilypond and editors

[Tapio Tuovila]

Frédéric Chiasson kirjoitti:
Well, I never tried jEdit on Mac. But I tried it on PC and the 
LilypondTool didn't work out and I had so many problems that I 
discarded it after a week.
On the other hand, I have used jEdit with LilypondTool on PC (SuSE and 
Ubuntu linux) for over two years on almost daily basis; here this 
combination has worked all the time and has grown better and better, 
(IMHO, that is. )


So I would like to encourage anybody to give jEdit at least a try, I 
find jEdit with LilypondTool quite an effective tool.


my best wishes,
Tapio



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Wikis

[Kevin Dalley]

Yes, and no.  I could spend 15 minutes, and mail it off to Graham, but
I probably won't.  The official document seems much more serious, and
deserves much more thought than 15 minutes, therefore I may never do
it.

Nevertheless, I may give it a try.

Graham Percival <[EMAIL PROTECTED]> writes:

> Kevin Dalley wrote:
>> The nice thing about a wiki is that I can spend 15 minutes improving
>> the one area which I now understand after spending an hour
>> researching.
>
> The same applies to the main docs!  Spend 10 minutes making a good
> small lilypond example, spend five minutes writing two or three
> sentences explaining the example, then email it to me.
>
> http://lilypond.org/web/devel/participating/documentation-adding
>
> - Graham


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user