Hello list,
I am now using lilypond 2.14 and have a question to the newly introduced
\footnote command:
What grobnames are allowed?
The following works as expected:
--snip--
\relative c'' {
\footnoteGrob #'NoteHead #'(1 . 1) \markup { \super "*" } \markup {
\line { \super "*" my explanatio
Hello,
I'm trying to break up a project into smaller files. I have global
definitions in one file (global.ily), the main \score block in
main.ly, and each part of the score in separate files. When I had
everything in a single file, I had no issues compiling, but putting
the definitions in their ow
Thanks for raising the topic. I've been extracting small examples using
Gimp. I'll have to try -dpreview!
Regards,
Bruys
On Fri, Jun 24, 2011 at 2:59 AM, Ralf Mattes wrote:
> On Thu, 23 Jun 2011 12:23:28 +0200, Federico Bruni wrote:
>
> > you are missing the option -dpreview
> > it's explained i
- Original Message -
From: "Jacek Gajek"
To:
Sent: Thursday, June 23, 2011 4:16 PM
Subject: ERROR: Unable to find file "ice-9/boot-9.scm" in load path
Hello, I encounter the following output, no matter how do I try to use
lilypond from cmd.
"lilypond-windows" drag&drop works, but I w
- Original Message -
From: "Jesse Engle"
To:
Sent: Friday, June 24, 2011 9:36 AM
Subject: Breaking up project into smaller files
Hello,
I'm trying to break up a project into smaller files. I have global
definitions in one file (global.ily), the main \score block in
main.ly, and each
On Jun 24, 2011, at 10:15 AM, Jan-Peter Voigt wrote:
> Hello list,
>
> I am now using lilypond 2.14 and have a question to the newly introduced
> \footnote command:
> What grobnames are allowed?
> The following works as expected:
> --snip--
> \relative c'' {
>\footnoteGrob #'NoteHead #'(1 .
On Fri, Jun 24, 2011 at 10:35:48AM +0100, Phil Holmes wrote:
> - Original Message - From: "Jesse Engle"
> >explain. Here is a link to program input and output:
> >http://www.pastie.org/2115133
>
> I can't test this without a fair bit of work to get rid of all the
> numbers on the left of t
Connor Harris wrote:
>
>
> When the top voice has dynamic markings, though, Lilypond places the
> lyrics
> above the dynamics. The results are suboptimal, with large amounts of
> space
> between the lyrics and dynamics. I want to be able to position dynamics
> above
> lyrics to leave less space
> I'm trying to break up a project into smaller files. I have global
> definitions in one file (global.ily), the main \score block in
> main.ly, and each part of the score in separate files. When I had
> everything in a single file, I had no issues compiling, but putting
> the definitions in their
I see that there are some older messages complaining about the way Lilypond
handles slurs going across system breaks. I thought I would add my voice,
since this is a very common thing occurrence, and the fact that it is
handled so poorly while other less common issues are handled well is rather
s
On Fri 24 Jun 2011, 05:21 MusFelix wrote:
> My main complaints are two:
>
> 1. The slur BEFORE the break should not have such a steep slope. If a the
> slur goes from a C to the same C , the slur should be horizontal. And if
> the slur goes to a higher or lower note, the slope should _slightly_
- Original Message -
From: "MusFelix"
To:
Sent: Friday, June 24, 2011 1:21 PM
Subject: Slurs across system breaks are not good
I see that there are some older messages complaining about the way
Lilypond
handles slurs going across system breaks. I thought I would add my voice,
sin
Hello,
From: lilypond-user-bounces+james.lowe=datacore@gnu.org
[lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of MusFelix
[musfe...@live.com]
Sent: 24 June 2011 13:21
To: lilypond-user@gnu.org
Subject: Slurs across system breaks are
On Fri, Jun 24, 2011 at 05:21:19AM -0700, MusFelix wrote:
>
> I see that there are some older messages complaining about the way Lilypond
> handles slurs going across system breaks. I thought I would add my voice,
> since this is a very common thing occurrence, and the fact that it is
> handled s
Philip,
Here is an example of the first issue---sloping, and even in the wrong
direction---(it seems to occur only when a rest is involved):
\version "2.14.1"
\paper{ ragged-right=##t }
\relative c' {
\clef bass
d4 d d( r \break d')
}
The other issues all appear to be reported alre
Greetings again,
since I mostly typeset folk songs, I need a lot of \partial measures
(e.g. at the end or at repeats).
I can't understand why LilyPond since 2.13.xx throws warnings that
\partial is only allowed at the beginning of a score.
The manual says, I should use a monster like "\se
Hello fellow pond-dwellers,
I'd like to print chords like "c/e" as chord names with "E" as a small
index to "C" or even "stacked" with a small E below a normal-sized C,
without the slash.
How can I achieve that? I didn't find anything like that in the docs
nor LSR.
Perhaps I misunderstand
On Fri, Jun 24, 2011 at 05:57:38PM +0200, Henning Hraban Ramm wrote:
> Can someone explain why this was changed? (And I really would like
> to continue using \partial or some other simple command!)
Search the mailing list archives for the discussion which prompted
the change in the first place. I
Hello,
From: lilypond-user-bounces+james.lowe=datacore@gnu.org
[lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of Henning
Hraban Ramm [hra...@fiee.net]
Sent: 24 June 2011 16:41
To: LilyPond User
Subject: chord names with lowered bass
Am Freitag, 24. Juni 2011, 17:57:38 schrieb Henning Hraban Ramm:
> Greetings again,
>
> since I mostly typeset folk songs, I need a lot of \partial measures
> (e.g. at the end or at repeats).
You don't need to use \partial for the final measure or repeats at all. I.e.
it is perfectly fine to use
On 6/24/11 9:41 AM, "Henning Hraban Ramm" wrote:
> Hello fellow pond-dwellers,
>
> I'd like to print chords like "c/e" as chord names with "E" as a small
> index to "C" or even "stacked" with a small E below a normal-sized C,
> without the slash.
> How can I achieve that? I didn't find anythi
On Fri, Jun 24, 2011 at 11:57 AM, Henning Hraban Ramm wrote:
> Greetings again,
>
> since I mostly typeset folk songs, I need a lot of \partial measures (e.g.
> at the end or at repeats).
>
> I can't understand why LilyPond since 2.13.xx throws warnings that \partial
> is only allowed at the begin
On Jun 24, 2011, at 10:41 AM, Henning Hraban Ramm wrote:
> Hello fellow pond-dwellers,
>
> I'd like to print chords like "c/e" as chord names with "E" as a small index
> to "C" or even "stacked" with a small E below a normal-sized C, without the
> slash.
> How can I achieve that? I didn't find
On 6/24/11 9:57 AM, "Henning Hraban Ramm" wrote:
> Greetings again,
>
> since I mostly typeset folk songs, I need a lot of \partial measures
> (e.g. at the end or at repeats).
Mostly I don't think you need \partial measures. You can just put a \bar
command in the middle of a measure to end
Am 2011-06-24 um 18:56 schrieb Marc Mouries:
I like you was initially surprised that \partial are only allowed at
the beginning. However I found that this can be avoided by simply
moving the repeat sign. Example: Usually fold songs are written like
this:
\time 4/4 |: a8 | .. | ...
Am 2011-06-24 um 18:55 schrieb Reinhold Kainhofer:
You don't need to use \partial for the final measure or repeats at
all.
Thank you for the hint - it didn't occur to me to try, since it seemed
necessary in earlier versions.
BTW: Some songbooks use partial measures at every start and end
Am 2011-06-24 um 18:38 schrieb James Lowe:
http://lsr.dsi.unimi.it/LSR/Snippet?id=459
?
You want to use a \super markup perhaps?
No, I asked about *chord names*. Perhaps I wasn't clear enough.
\context ChordNames {
\chordmode { g/b }
}
prints like "G/B".
But I'd like it to print like (H
Dear list,
In one piece I am working on, I have had to add the Bar_number_engraver to
the Staff context, and have at one point used \set Staff.currentBarNumber to
change the current bar number. Unfortunately, this effect seems to be
permanent, i.e. the bar number stops advancing by 1 every bar aft
Am Freitag, 24. Juni 2011, 18:56:00 schrieb Marc Mouries:
> I like you was initially surprised that \partial are only allowed at the
> beginning. However I found that this can be avoided by simply moving the
> repeat sign. Example: Usually fold songs are written like this:
> \time 4/4 |: a8 | ..
Colin Campbell wrote:
On 11-06-24 05:50 AM, James Lowe wrote:
As far as I can tell for 'normal' use where someone installs,
uninstalls and installs the next version it all works.
But not if we keep installing new versions again and again.
I'm not sure it's that straightforward. I've always u
On Thu, Jun 23, 2011 at 1:53 PM, Graham Percival
wrote:
> Please stop capitalizing "patch". If you're referring to issue
> 1264, the patch broke the build, and in any case it's postponed
> until GLISS.
Er, no it didn't. (TBH, I do remember Neil noticing a very minor,
unrelated error though.)
The
On Sat, Jun 25, 2011 at 12:44:30AM +0200, Valentin Villenave wrote:
> On Thu, Jun 23, 2011 at 1:53 PM, Graham Percival
> wrote:
> > Please stop capitalizing "patch". If you're referring to issue
> > 1264, the patch broke the build, and in any case it's postponed
> > until GLISS.
>
> Er, no it di
On Fri, Jun 24, 2011 at 4:00 PM, Reinhold Kainhofer
wrote:
> Am Freitag, 24. Juni 2011, 18:56:00 schrieb Marc Mouries:
> For a better understanding and some examples, I would recommend LilyPond's
> notation reference:
> http://kainhofer.com/~lilypond/Documentation/notation/long-repeats.html
>
> >
On Fri, Jun 24, 2011 at 1:36 PM, Henning Hraban Ramm wrote:
> Am 2011-06-24 um 18:56 schrieb Marc Mouries:
>
>
> I like you was initially surprised that \partial are only allowed at the
>> beginning. However I found that this can be avoided by simply moving the
>> repeat sign. Example: Usually fo
On Fri, Jun 24, 2011 at 6:44 PM, Valentin Villenave
wrote:
>
> If you have some time, please do read
> http://lilypond.org/doc/v2.15/Documentation/extending/scheme-in-lilypond
> and
> http://www.gnu.org/software/guile/manual/
> it makes for a fascinating reading reading experience, at least if
> y
On 11-06-24 09:58 AM, MusFelix wrote:
Philip,
Here is an example of the first issue---sloping, and even in the wrong
direction---(it seems to occur only when a rest is involved):
\version "2.14.1"
\paper{ ragged-right=##t }
\relative c' {
\clef bass
d4 d d( r \break d')
}
The other
Colin Campbell writes:
> This sounds like Phil's comment in issue 1625, but I'm thinking that
> this should be a Known Issue in the Notation Reference, given that
> slurs across rests or breaks are both problematic.
Since you can't sensibly avoid either, this really warrants fixing.
--
David K
37 matches
Mail list logo
