Robin Bannister wrote:
> (a solution to my problem)
Thanks, Robin. I had actually found and tried #2, but didn't realize
that I needed to replace my R's with r's. #1 was new to me.
All is now well.
--
Tim Walters | The Doubtful Palace | http://doubtfulpalace.com
__
Tim Walters wrote:
Is there any way to [...] leave the same amount of white space
as would be used if lyrics/chords were present?
This amount can vary.
The vertical space allotted depends on what is being typeset;
e.g. Cm needs less height than Cm7
Based on a discussion last September
>> > IIUC, one interesting advantage of this is that scheme symbols
>> > have less restrictions than parser identifiers:
>> >
>> > \anchor #'m.32
>> > \anchor #'flute2-entrance
>>
>> Mhmm, this is not something we should advertize loudly...
>
> Why not?
I believe it confuses users that Scheme code
Werner LEMBERG wrote:
> > IIUC, one interesting advantage of this is that scheme symbols
> > have less restrictions than parser identifiers:
> >
> > \anchor #'m.32
> > \anchor #'flute2-entrance
>
> Mhmm, this is not something we should advertize loudly...
Why not?
- Mark
__
> IIUC, one interesting advantage of this is that scheme symbols
> have less restrictions than parser identifiers:
>
> \anchor #'m.32
> \anchor #'flute2-entrance
Mhmm, this is not something we should advertize loudly...
Werner
___
lilypond-user
Thanks, I'll keep that in mind.
-Jonathan
--- On Tue, 8/4/09, Mark Polesky wrote:
> From: Mark Polesky
> Subject: Re: First Lilypond Score
> To: "Valentin Villenave" , "Jonathan Wilkes"
>
> Cc: "lilypond-user Mailinglist"
> Date: Tuesday, August 4, 2009, 6:32 PM
>
> Valentin Villenave wro
Jay Anderson wrote:
> global =
> {
> \time 4/4 s4*4*10
> \time 3/4 s4*3*5
> \time 7/4 s4*7
> \time 4/4 \anchor #'coda s4*4*10
> \bar "|."
> }
>
> \addAt #'coda \global {\tempo \markup "Extremely slow"}
IIUC, one interesting advantage of this is that scheme symbols
have less restrictions tha
Valentin Villenave wrote:
> > But I don't see the bug listed in the google code page for bugs.
>
> That's because you have to check our bug mailing list:
> http://lists.gnu.org/archive/html/bug-lilypond/2007-01/msg00069.html
Alternatively you can change the "Search within" option from
"Open is
Mats Bengtsson wrote:
The [ belongs to the note that starts the beam, whereas the \override
command is inserted between notes, so the correct syntax is
d8[ \override NoteHead #'style = #'cross d] ~ d4
Many thanks!
___
lilypond-user mailing list
lil
The [ belongs to the note that starts the beam, whereas the \override
command is inserted between notes, so the correct syntax is
d8[ \override NoteHead #'style = #'cross d] ~ d4
/Mats
Michael Käppler wrote:
Hi all,
can somebody explain, why the following doesn't work with manual
beaming,
Hi all,
can somebody explain, why the following doesn't work with manual
beaming, but with autobeaming?
\version "2.13.4"
\relative c' {
\time 2/4
d8 \override NoteHead #'style = #'cross d ~ d4 % This works fine
% \autoBeamOff
% d8 \override NoteHead #'style = #'cross [d] ~ d4
}
The second re
Greetings everyone,
as the -devel list tends to get crowded these days, John and I have
opened a separate mailing list for documentation translators.
You can subscribe and read the archives on http://lists.lilynet.net/translations
To whomever is in charge of the translationproject.org LilyPond
c
On 8/4/09 5:35 AM, "Reinhold Kainhofer" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Dienstag, 4. August 2009 01:29:56 schrieb Trevor Daniels:
>> Jonathan
>>
>> Stupid of me! I gave the correct analysis of
>> your problem but the wrong solution!
>>
>> You should use a ph
2009/8/4 Mats Bengtsson :
> See http://code.google.com/p/lilypond/issues/detail?id=75
Thanks! I was looking at 304, but that wasn't it :)
Regards,
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lily
See http://code.google.com/p/lilypond/issues/detail?id=75
/Mats
Valentin Villenave wrote:
2009/8/4 Mats Bengtsson :
Right! That's one reason that we have a bug report on this problem.
I'm sure I've already seen similar problems, but I can't find it anywhere.
Jonathan, would you li
Felix Krause wrote:
Hi all,
I have two problems with endings of volta repeats:
1) I have a volta repeat with an alternative ending, like this:
\override Score.BarNumber #'break-visibility = #'#(#t #t #t)
\repeat volta 2 { r4 f r f }
\alternative { { r f r f } { r f r a, } }
d a d a
The two
2009/8/4 Mats Bengtsson :
> Right! That's one reason that we have a bug report on this problem.
I'm sure I've already seen similar problems, but I can't find it anywhere.
Jonathan, would you like to send a bug report (preferably with lyrics
and melismas, as Reinhold suggested), to the bug-lilyp..
2009/8/4 Graham Percival :
> Why do people never believe me when I say that there's tons of
> cool stuff we /could/ do, if only more people helped out?
That's not my point. My point is to make sure that nothing potentially
cool gets lost.
> Of course, there's no point writing the sequel until th
2009/8/1 Valentin Villenave :
>> The Spanish forum is a Yahoo! group.
>
> There's also
> http://www.lilypondforum.de/ (German)
> http://groups.google.com/group/lilypond-brasil (Portuguese)
> http://lists.gnu.org/mailman/listinfo/lilypond-user-fr (French)
... and http://www.lilypondforum.nl/ (Dutch
Reinhold Kainhofer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 4. August 2009 01:29:56 schrieb Trevor Daniels:
Jonathan
Stupid of me! I gave the correct analysis of
your problem but the wrong solution!
You should use a phrasing slur, \( .. \)
instead of a slur, ( .
On Tue, Aug 04, 2009 at 12:42:15PM +0200, Valentin Villenave wrote:
> 2009/8/4 Graham Percival :
> > There you go:
> > http://lists.gnu.org/archive/html/lilypond-devel/2005-11/msg00024.html
>
> This is huge! (I suspect I wasn't subscribed to -devel when this was
> posted, otherwise I'd have notice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 4. August 2009 01:29:56 schrieb Trevor Daniels:
> Jonathan
>
> Stupid of me! I gave the correct analysis of
> your problem but the wrong solution!
>
> You should use a phrasing slur, \( .. \)
> instead of a slur, ( .. ). Then the acciacc
2009/8/1 Jonathan Wilkes :
> I found that layout-set-staff-size not affecting staff line spacing in a
> layout block was addressed in a previous email as a bug:
> http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00034.html
>
> But I don't see the bug listed in the google code page for bug
2009/8/4 Han-Wen Nienhuys :
> I can imagine how this would be implemented, but it would be a lot of
> work. If anyone is up for a challenge, I can give some pointers. :)
OK, now there's no way I'm gonna let you get away with such a promise :-)
http://code.google.com/p/lilypond/issues/detail?id=82
2009/8/4 Graham Percival :
> There you go:
> http://lists.gnu.org/archive/html/lilypond-devel/2005-11/msg00024.html
This is huge! (I suspect I wasn't subscribed to -devel when this was
posted, otherwise I'd have noticed it).
Even though there's clearly no magic recipe to speed up LilyPond
(except
Lilypond import for MuseScore is very very limited, but export is a little
more elaborated. So don't expect it to be funtional for full scores.
Most of the development work is done by Olavgun. You can see
http://www.ohloh.net/p/musescore/contributors/48848810665750 his commits
over the past year
Look for "swing" in the LSR.
http://lsr.dsi.unimi.it/LSR/Search?q=swing
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
27 matches
Mail list logo
