Rhythms with no staff lines but with bar lines

Hello, I want to display rhythms without the staff, but with bar lines. I removed the Staff_symbol_engraver from the context of the Staff and attempted to add the Bar_engraver to the context of the Voice. The staff lines are gone but there are no bar lines. I am using version 2.11: \new Staff

Re: Accent and unaccent signs

Damian leGassick mac.com> writes: > there's a few things to do and a few different places to look in the > docs - if you search for unicode or utf8 it covers it > > then you can use the unicode 02D8 or UTF8 CB 98 for the breve (or 0306/ > CC 86 for the 'combining breve') > > the acute is 00B4

Different line breaks in parts

I am trying to produce a small score for a quartet and parts. What I am trying to do is to be able to specify different line breaks for each part. Because the note density is different for each part, Lilypond produces parts that are too dense for my taste. I would like to have the music mor

Re: *.mid vs *.midi

On 18 May 2008, at 22:47, immanuel litzroth wrote: I am talking about C. That was what my argument was about. Now you bring C++ -- Has somebody pointed out to you that that is a different standard? -- into the argument saying out that it does not have a "formal grammar". Are you making this

Re: horizontally aligning columns in \fill-line

Reinhold: > In one of my scores, I'm writing two pages with the lyrics of a mass, > together > with the corresponding German/English translations. I'm using > \fill-line { > \column{"Latin text"...} > \column{"German text"...} > \column{"English text"...} > } > to generate the three colu

Re: *.mid vs *.midi

On 18 May 2008, at 19:55, immanuel litzroth wrote: So the C language itself does not have any #include directive. The C language standard is available at: http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1256.pdf You'll see all the preprocessing directives explained there and no mention of a

Re: *.mid vs *.midi

Quoting Hans Aberg <[EMAIL PROTECTED]>: > On 18 May 2008, at 15:16, immanuel litzroth wrote: > > >> So the C language itself does not > >> have any #include directive. The C language standard is available at: http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1256.pdf You'll see all the preproces

Re: horizontally aligning columns in \fill-line

Le 18 mai 08 à 17:30, Reinhold Kainhofer a écrit : In one of my scores, I'm writing two pages with the lyrics of a mass, together with the corresponding German/English translations. I'm using \fill-line { \column{"Latin text"...} \column{"German text"...} \column{"English text"...} } to ge

Re: Setting a global default for the \paragraph macro (NR Section 7.4.4)?

Le 18 mai 08 à 16:46, Reinhold Kainhofer a écrit : In the NR in Section 7.4.4 (http://lilypond.org/doc/v2.11/Documentation/user/lilypond/New-markup-list-command-definition ) there is a definition of the \paragraph markup list command, which indents the first line by the value of the property

horizontally aligning columns in \fill-line

In one of my scores, I'm writing two pages with the lyrics of a mass, together with the corresponding German/English translations. I'm using \fill-line { \column{"Latin text"...} \column{"German text"...} \column{"English text"...} } to generate the three columns. However, since the mass

Re: launch scripts (was: *.mid vs *.midi)

On 18 May 2008, at 14:56, fiëé visuëlle wrote: I used the existence of a PDF as indicator if LilyPond was successful - it says "file failed" very often even if the output is ok. OK. Perhaps Lilypond has the problem and not always produces the expected exit code. Also, you might put in

Setting a global default for the \paragraph macro (NR Section 7.4.4)?

In the NR in Section 7.4.4 (http://lilypond.org/doc/v2.11/Documentation/user/lilypond/New-markup-list-command-definition ) there is a definition of the \paragraph markup list command, which indents the first line by the value of the property 'par-indent. There is also an example how to overrid

Re: *.mid vs *.midi

On 18 May 2008, at 15:16, immanuel litzroth wrote: So the C language itself does not have any #include directive. Implementation issue. There is no requirement for a separate preprocessor, ... In the C and C++ standards there are. ...and the fact that compilation happens in stages is a fe

Re: initial .ly files [was Re: *.mid vs *.midi]

Nicolas: > Le 18 mai 08 à 00:24, Karl Hammar a écrit : > > > Actually what I would like is some way to tell on the command line > > that > > this run should have /ancient fonts/c-clefs/modern clefs/... so I > > could > > easily switch style without having to write a new file. > > You can alre

Re: *.mid vs *.midi

Quoting Hans Aberg <[EMAIL PROTECTED]>: > C is composed of two languages: the preprocessor, to which #include > > belongs, and merely composes the files into one compile unit, and > the > C compiler, which processes that. So the C language itself does not > > have any #include directive.

Re: launch scripts (was: *.mid vs *.midi)

Am 2008-05-18 um 13:57 schrieb Hans Aberg: This is my lily.sh script for OSX: - deletes previous myname.pdf - runs lilypond myname.ly - deletes old mylily.mid and renames myname.midi to myname.mid - deletes myname.ps - opens MIDI and PDF You don't have to remove older files, as they are over

Re: Accent and unaccent signs

there's a few things to do and a few different places to look in the docs - if you search for unicode or utf8 it covers it then you can use the unicode 02D8 or UTF8 CB 98 for the breve (or 0306/ CC 86 for the 'combining breve') the acute is 00B4/C2 B4 and 0301/CC 81 is the combining acute.

Re: launch scripts (was: *.mid vs *.midi)

On 18 May 2008, at 12:55, fiëé visuëlle wrote: This is my lily.sh script for OSX: - deletes previous myname.pdf - runs lilypond myname.ly - deletes old mylily.mid and renames myname.midi to myname.mid - deletes myname.ps - opens MIDI and PDF You don't have to remove older files, as they are

Re: launch scripts (was: *.mid vs *.midi)

Am 2008-05-18 um 12:16 schrieb Hans Aberg: On UNIX, like OS X, one can run the command lilypond foo.ly && mv foo.midi foo.mid Easy to repeat - on OS X, use the up arrow key. Or write a script or alias. This is my lily.sh script for OSX: """ #!/bin/bash if [ -e $1.pdf ]; then rm $1.

Number Repeated Measures

Hi, I wonder if anyone could offer me some help to improve the scheme function I wrote below. The function numberedRepeats works in a similar way to "\repeat unfold", except it numbers the repeated measures without replacing them with percent-like signs. There is a problem, which I lack suffici

Re: Audio signal to generate .ly file

On Thu, 2008-05-15 at 08:51 -0400, Kieren MacMillan wrote: > True... but check out id=dna&L=0>. This is VERY scary... -- Mark Knoop ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/m

Re: *.mid vs *.midi

On 18 May 2008, at 10:34, Valentin Villenave wrote: and if you are using makefiles, lilypond don't have to solve that problem, you could just as easily add an mv-line in the makefile. If we all were using makefiles (including the newbies on Win32), then we wouldn't be having this discussion at

Re: *.mid vs *.midi

2008/5/18 Karl Hammar <[EMAIL PROTECTED]>: > and if you are using makefiles, lilypond don't have to solve that > problem, you could just as easily add an mv-line in the makefile. If we all were using makefiles (including the newbies on Win32), then we wouldn't be having this discussion at all :-)

Accent and unaccent signs

How do I get these articulations? The accent sign I mean is shaped like an acute accent (aigu) in French, and the unaccent sign is like a saucer (or a breve in old-fashioned printing of Latin). There's nothing like them defined in font-table.ly. Is there a way to define scripts to use other fo