Hi Urs,
On Sat, Sep 28, 2013 at 12:13 PM, Urs Liska wrote:
> Hi,
>
> I have a 'function' that redefines commands like \slurUp to color the
> corresponding grob (highlighting manual interventions during score
> development).
>
> Is it possible to 'catch' instances of grobs whose direction has be
To the author of the new LSR-snippet "Center Lyric Syllables (ignoring
punctuation)"
Many thanks for your code.
I did some slightly reformatting of code and description.
It's now approved as
http://lsr.dsi.unimi.it/LSR/Item?id=888
Best,
Harm
___
li
Yep, that will do the trick. Thanks a lot, Phil.
As for the documentation, maybe it would be interesting to include at least
one example of filled path, such as the one we are using here. It is really
helpful for beginners such as myself to find tiny examples that you can
copy and modify for your
Hi,
I have a 'function' that redefines commands like \slurUp to color the
corresponding grob (highlighting manual interventions during score development).
Is it possible to 'catch' instances of grobs whose direction has been set by
the ^ and _ operators and call a music function on the affected
- Original Message -
From: Gilberto Agostinho
To: lilypond-user
Sent: Saturday, September 28, 2013 5:45 PM
Subject: filled path
Hi all,
I agree the documentation isn't clear on this, but a bit of searching and I
find:
\markup {
\override #'(filled . #t) \path #0.25 #samplePath
}
Hi all,
I would like to ask you a simple question: how do I make a filled path in
the example below? I can't find what is the correct syntax...
samplePath =
#'((moveto 0 0)
(lineto -1 1)
(lineto 1 1)
(lineto 1 -1)
(curveto -5 -5 -5 5 -1 0)
(closepath))
\markup {
\path
Thank you very much, rumor is now working.
I think that we have used more disk space, collectively, discussing whether
or not MIDI input to Lilypond will save time, than the rumor source code
takes up. And more time was probably spent in the discussion than will be
saved by using (or not using) MI
Peter Bjuhr writes:
> On the other hand, this doesn't work:
>
> \version "2.17.28"
>
> A = \relative c'' {a4 b c a ~ }
>
> \score {
> \new Staff
> { \A \A }
> }
That's because each \A is in a Voice of its own. Use an explicit Voice
to avoid independent implicit voices for each \A:
\score {
Dear friends,
October 16th, I'll release the new version of Frescobaldi. There are some
changes to the translatable strings, and a few new strings; so if you
can find some time, please update the translations for your languages.
This release also marks an important point in Frescobaldi develop
Steve Noland wrote:
I am having problems with some of the jazz chordnames engraving correctly.
Specifically, a Dm7(b5) chord (D minor 7, flat 5) ...
Check out this recent thread:
http://lists.gnu.org/archive/html/lilypond-user/2013-08/msg00568.html
Cheers,
Robin
___
On 09/28/2013 08:49 AM, Urs Liska wrote:
\version "2.17.26"
% How could I write the equivalent of
\drums { sn8 sn8 ~ sn8 sn8 }
%using variables?
% This does work!
A = \drummode { sn8 sn8 ~ }
\score {
\new DrumStaff
{ \A \A }
}
%end with a tie
{ b'4 a' g' b' ~ }
Best
Peter
Thanks.
I didn
On 09/28/2013 10:30 AM, David Kastrup wrote:
They are probably compiled, but that does not_install_ them. You
should be able to run LilyPond from out/bin/lilypond without installing
it.
Yes, if I'm not totally mistaken I have the system setup so that I have
the stable 2.16.2 version installed
When I add a custom option on the command line with -dcustom-option and
test for it in the input file using
#(if (defined? 'custom-option))
My file compiles well and respects the option, but I get a warning about
"No such internal option: custom-option" (maybe it's differently worded,
I'm tr
I'm following the Application Usage to define variables on the command line:
http://www.lilypond.org/doc/v2.16/Documentation/usage/command_002dline-usage.html#basic-command-line-options-for-lilypond
When I use the -e command line option and write
#(use-modules (guile-user))
at the beginning of
Peter Bjuhr writes:
> On 09/28/2013 09:27 AM, David Kastrup wrote:
>> There are only three rather glaringly obvious reasons I can think of:
>>
>> a) you are not running the rebuilt executable
>> b) the rebuilt executable is in a place where it accesses the old
>> engraver-init.ly
>> c) you ar
On 09/28/2013 09:27 AM, David Kastrup wrote:
There are only three rather glaringly obvious reasons I can think of:
a) you are not running the rebuilt executable
b) the rebuilt executable is in a place where it accesses the old
engraver-init.ly
c) you are looking at the wrong PDF file
If y
Peter Bjuhr writes:
> On 09/27/2013 01:43 PM, David Kastrup wrote:
>> I've committed a patch implementing grace autobeaming to
>> http://code.google.com/p/lilypond/issues/detail?id=3566>
>
> Hi David!
>
> I also wanted to contribute with some testing. I changed the files
> with your patched chang
17 matches
Mail list logo
