David Kastrup writes:
> Russell Cook writes:
>
>> \version "2.17.21"
>>
>> \score {
>> << \new Voice { \time 4/4 \tempo \markup { "Rubato " \concat { \smaller
>> \general-align #Y #DOWN \note #"4" #1 \medium "
ext is placed very close to the note"
> c^"This text is padded away from the previous text"
> c^"This text is placed close to the previous text" }
"No problem on Linux" with the GUB-compiled version or with a
self-compiled version? 32bit or 64bit?
t; skylined text alongside a staff consumes all memory under Windows
> http://code.google.com/p/lilypond/issues/detail?id=3432
I could imagine the problem might depend on font metrics, and we have
not been able to figure out yet why we see differences for them betwee
ure this is well
> explained...)
m would collide with the stem when placed right above the notehead. The
smaller letters fit.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
t; c''
> }
>
> Am I missing something? Or is ly:grob-system broken?
ly:grob-system only returns the system after is has been set in the
PaperColumn which is after line breaking. What you see as # above is a single system encompassing the entire score.
--
David Kast
solved.
So there is nothing wrong with answering whenever you find something
worthwhole to say.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
t; \key c \major
> \time 4/4
> \tempo 4 = 96
> c2 d
> e4. d8 c2
> }
>
> \score {
> \new Staff \melody
> }
Can't reproduce. Can you copy&paste the error message? Which LilyPond
version, operating system? Is this the official binary?
--
David Kast
Marek Klein writes:
> Hello,
>
> 2013/7/3 David Kastrup
>
>> ly:grob-system only returns the system after is has been set in the
>> PaperColumn which is after line breaking. What you see as #> System > above is a single system encompassing the entire score.
&g
eScripts and
MMRs
http://code.google.com/p/lilypond/issues/detail?id=1757>
and particularly the latter would already seem to cover the complaint.
> If so, the behavior you describe, Barikavily, is the intended
> behavior.
Not so much "intended" as "current and well-known limitation".
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ond.org/doc/v2.17/Documentation/snippets/rhythms#rhythms-beam-grouping-in-7_002f8-time
Well, we can put them into snippets/new and fix them, but that seems
backwards. Instead we should likely look where the conversion/import
goes wrong and fix _that_.
--
David Kastrup
Voice {\voiceTwo c1}>>
> <<{\voiceOne a1)}\new Voice {\voiceTwo c1}>>
> }
>
> the first slur is not connected
Starting and ending slur are in different voices (each started with a
separate \new Voice) so LilyPond does not consider them related.
--
David Kastrup
_
acing, nonstaff-unrelatedstaff-spacing etc. accept
> single values?
Have an example?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
w TabStaff {
>
> \relative c {
>
> d,,,1 e
>
> }
>
> }
Added as issue 3484
http://code.google.com/p/lilypond/issues/detail?id=3484>.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
hat's as good as it gets. I don't see a reasonably reliable way for
LilyPond to do second-guessing based on a particular instrument, and one
would not actually do the user much of a favor since a change of
instrument would suddenly cause a change of octave relations in the
score.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
is something wrong with the function or is it a bug in windows?
Well, much of LilyPond is not crash-safe if you stuff unexpected data
structures into semi-internal variables.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Eluze writes:
> David Kastrup wrote
>> This is totally confused. It defines bracketOpenSymbol as a vector
>> consisting of the symbol make-music and the list (quote Music). But it
>> puts these definitions in a list where they don't make sense. This is a
>> to
e closest to the note just before.
The closest note is a c (c below middle c'). c does not exist on a
banjo.
> But I found as a result of the responses that this idea is not liked
> very much,
The idea of just playing a different note than requested? Yes, it would
appear that thi
that this is just user error.
If the user error is triggered by bad documentation, this can lead to a
problem report for the documentation on the bug list again.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
"that" should be replaced by "than"
I'm going to push a fix straight to staging, no need for an issue here.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
bb writes:
> Am 04.08.2013 14:27, schrieb David Kastrup:
>> bb writes:
>>
>>> It is impossible to set slurs inside triples.
>> Wrong.
>>
>>> Is a widely used practice to mark swing rhythm. And I found it
>>> impossible to beam an eighth w
bb writes:
> Am 04.08.2013 16:21, schrieb David Kastrup:
>> bb writes:
[...]
>>> Try this:
>> And then an example where the rhythms don't add up and it is quite
>> unclear what it is supposed to show. And the entire text for all of
>> that is "T
Pond does not at the current point of time support different
parallel durations within a single voice.
See the whole of
http://code.google.com/p/lilypond/issues/detail?id=984>.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ashism, yes. Personally, I prefer using case/esac for almost
everything. That usually is quite more flexible and has been a shell
builtin for quite longer than test.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
e track will be doubled, so the file size will be
> double as well as the music (which may results in unattended consequences,
> like having acoustic and nylon guitar playing at the same time)
Should we remove it by default and add it back when using
\TabFullNotation
Federico Bruni writes:
> 2013/8/8 David Kastrup
>
>> Federico Bruni writes:
>>
>> > I've read this message:
>> > http://lists.gnu.org/archive/html/lilypond-user/2013-08/msg00148.html
>> >
>> > and I've realized something I
mp$ convert-ly spacing-convert-rules.ly
[...]
> \paper {
> markup-system-spacing = #'((basic-distance . 20) (minimum-distance . 10))
> system-system-spacing = #'((basic-distance . 20))
> }
The file itself continues to contain the old settings? Not that some
unrelated experi
Federico Bruni writes:
> 2013/8/10 David Kastrup
>
>> The file itself continues to contain the old settings? Not that some
>> unrelated experiment or editing or whatever overwrote it?
>>
>
> Yes, same settings and I never edited it again.
> After few hours I u
;d like to discuss
there.
See http://www.lilypond.org/contact.html> for a list of contact
points for various occasions.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
y since first the expression is read and recognized as
SCM_TOKEN which is not combinable with the assignment (usually), then
the assignment is executed, and only then the expression read with
#(...) is evaluated and can already rely on the new value of the
variable.
But since \ needs to make a choic
Marek Klein writes:
> Hello David,
> do we need a tracker issue for this?
>
> Marek
>
> 2013/8/5 David Kastrup
>
>> Thomas Klausner writes:
>>
>> > Hi!
>> >
>> > The latest stable and development branches of lilypond do not compile
gt;1-\markup { "+" }
Nothing there with the slightest similarity to a REAL. Perhaps remnants
from a compilation eith different tools: try make clean.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
7;t know anything about the Windows command line. What happens if
you remove the space between > and mynewfile.ly ?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Eluze writes:
> Phil Holmes-2 wrote
>> "
>> I presume convert-ly runs OK without the > redirect? Does dir > dir.txt
>> work OK?
>
> yes, with the option -e, and also dir > dir.txt
And without option -e (the output should th
for (unless you exceed the allotted quota or
physical space on the device). I seem to remember that Windows is quite
more iffy about those kinds of thing.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
gt;>
>> which is quite unspectacular. So either there is still a permission
>> problem, or your version of Python and Windows just don't cooperate
>> sensibly on sys.stdout.
>
> after looking up Martin Tarenskeen's indent-ly.py I replaced
>
&
likely not a good idea. I think it would be
reasonable if convert-ly only closed files it opened itself.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Colin Campbell writes:
> On 13-08-17 03:48 PM, David Kastrup wrote:
>> Eluze writes:
>>
>>> sorry, I ran the wrong program
>>>
>>> but now I get little more information:
>>>
>>> Traceback (most recent call last):
>>>F
ython\book_latex.py", line 206,
> in get_latex_textwidth
> returncode = os.system(cmd)
> KeyboardInterrupt
Seems like our version of Python does not cooperate with Windows 7.
This is likely the same problem as
http://code.google.com/p/lilypond/issues/detail?id=3510>
Maybe try
gt;
>
> Hi,
>
> I rarely use lilypond-book (if I do, with the manual on a second
> screen), so if I write nonsense, ignore!
> Though, for me it looks like \notes isn't defined in your example.
Sure, but that's no reason to hang.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
utput on 2.17.24 is fine.
There is no real candidate for such a difference in the commits. So did
you choose a significantly different directory name for building
2.17.25?
Or does it make a difference if you revert
commit de179d8b2cbf6fe86ff9a000a0d21bc6bc118905
Author: David Kastrup
Dat
e: missing operand
> Try `dirname --help' for more information.
That looks quite fishy, like a script getting confused by strange
circumstances.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
.)):
> /scratch/wip/lilypond-devel24/work/lilypond-2.17.24/out/share/lilypond/current/scm/chord-entry.scm:116:16:
> Wrong type argument in position 1 (expecting Pitch): 1
Ok, now we are getting somewhere. Not anywhere making much sense, mind
you. The change in question would appear to b
an empty file.
If you want to be on the safe side, write
make all >make.log 2>&1
since this will work on all shells known to me.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ompilation. No problem whatsoever. Huh.
And parser.cc does start with
/* A Bison parser, made by GNU Bison 3.0. */
/* Bison implementation for Yacc-like parsers in C
Copyright (C) 1984, 1989-1990, 2000-2013 Free Software Foundation, Inc.
[...]
So this can't be _all_ that's involved.
music function
arguments of type scheme? be somewhat similar.
Since "proper" assignments often involve music, and they are often
disambiguous because of being at top level, one should probably just
focus on the "scheme? argument" and "
need BISON anyway, and it's not like LilyPond
is a component for bootstrapping Bison or GCC or whatever else, so there
is no hen-and-egg problem we need to circumnavigate.
At any rate, the following commit should be related to the problem in
that it makes it possible to occur in the fir
Pierre Perol-Schneider writes:
> Hi David, hi Harm,
>
> 2013/8/31 David Kastrup
>
>>
>> An override is not a music function, so this is not strictly covered by
>> issue 3471. Actually, 1.0 is accepted just fine. It is just that we
>> are in music mode, and
Pierre Perol-Schneider writes:
> 2013/8/31 David Kastrup
>
>>
>> This can't really be "clarified" at a reasonably user-accessible level.
>>
>
> Well "clarfied" is probably not the right word, sorry for my bad english.
> What I meant w
Thomas Klausner writes:
> I've followed the thread and can confirm that
> rm lily/out/parser.*
> before building lilypond fixes the problem for me.
Can you also report which of the preexisting files in lily/out/ gets
overwritten by the problematic build, and which not?
--
roken
dependencies, we should fix them first anyway as they are still going to
cause problems for people _rebuilding_ LilyPond.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
real reason. I am somewhat at
a loss for the real reason, though.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
17.25/lily/out/parser.o
I took a look at the tar file. The time stamps of parser.cc, parser.hh
and parser.yy are identical as far as I can see which is not helpful for
make. Maybe we should take a look at the process creating the tar file.
--
David Kastrup
David Kastrup writes:
> Thomas Klausner writes:
>
>>> Can you also report which of the preexisting files in lily/out/ gets
>>> overwritten by the problematic build, and which not?
>>
>> The header file is not recreated, but the cc file is:
>>
>&g
ot just the clef glyph that is prominently broken, but also a number of
other frequent glyphs like the flags.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
t parties in time.
So far, I've been juggling with binaries to avoid the problem, but
that's no working solution for a distribution, in particular not one
compiled from source.
Is there a clear picture somewhere about what causes the problem? And a
reliable recipe for avoiding it?
--
Da
ugzilla.novell.com/show_bug.cgi?id=838374
For Ubuntu, reported as
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1220653>
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Marek Klein writes:
> Hello Werner,
>
> 2013/9/3 Werner LEMBERG
>
>> I suggest that we exclude the affected mpost versions in lilypond's
>> configure script.
>>
> do we need a tracker issue for this?
I think so. Better not to lose
ny for \midi. You only declare them for
\layout.
> This appears to be similar to
> http://lists.gnu.org/archive/html/lilypond-user/2013-09/msg00261.html
It is utterly unrelated.
> Example code is at
> http://github.com/openlilylib/snippets/blob/master/templates/predefined
entry=0, end=end@entry=2147483647)
at axis-group-interface.cc:580
#19 0x0814f365 in Hara_kiri_group_spanner::pure_height (smob=0xf6f3eb38,
start_scm=0x2, end_scm=0xf678c740) at hara-kiri-group-spanner.cc:58
So it looks like Item::break_status_dir is called on a null pointer
Item.
--
Dav
More a matter of curiosity than
anything else, though: the backtrace should in all likelihood be
sufficient for pinpointing the problem in the current code base.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
David Kastrup writes:
> Rutger Hofman writes:
>
>> On 09/12/2013 10:54 AM, Thomas Morley wrote:
>
>>> programming error: stopped tuplet bracket has neither left nor right bound
>>> no segfaut, though.
>>
>> It reports this error but does not core dum
David Kastrup writes:
> David Kastrup writes:
>
>> Rutger Hofman writes:
>>
>>> On 09/12/2013 10:54 AM, Thomas Morley wrote:
>>
>>>> programming error: stopped tuplet bracket has neither left nor right bound
>>>> no segfaut, tho
lines. The two values required multiply the staff line
thickness with the staff line spacing and are then added together to
give the ledger line thickness.
"doesn't sound good" is the understatement of the year. Yes, this
description is most definitely very, very wrong.
--
certain cases
>> the clef will be printed far away from its actual position. Minimal
>> example:
>
>
> I don't understand why the invisible barline is there. What's the
> point of it?
Minimal example, I presume. Still would be interestin
sion of LilyPond. The
conversion is one-way, though: once you upgraded the syntax, you can't
downgrade it again.
http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly>
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
line.)
>
> Obviously a workaround is to *manually* force a repeat bar at the
> beginning of measure 5 (with a '\bar "|:"' instruction),
Doesn't work. You can't have more than one bar type on one time step.
But you can have a complex bar type li
les this issue: https://codereview.appspot.com/6594047
>
> For me, this is clearly a backwards incompatibility.
Well, the commit message is
commit 38a4081efa4a8ee2f5da780ca0ed2991627afc46
Author: David Kastrup
Date: Sun Sep 30 02:21:00 2012 +0200
Issue 2869: Regularize lyrics lexer
David Kastrup writes:
> Vik Reykja writes:
>
>> Upgrading from 2.14.2 (Ubuntu 12.10) to 2.17.27 (git head) in order to try
>> something, I noticed my music was broken. Here is a minimal example
>> illustrating the problem:
>>
>> \new Lyrics \lyricmode { \
Vik Reykja writes:
> On Sun, Sep 22, 2013 at 6:39 PM, David Kastrup wrote:
>
>> David Kastrup writes:
>>
>> > Vik Reykja writes:
>> >
>> >> Upgrading from 2.14.2 (Ubuntu 12.10) to 2.17.27 (git head) in order to
>> try
>> >> so
cker for my comment. I don't think it makes
sense to diverge from established conventions here: a lot of tools and
version control systems know how to interpret the conventions currently
in use.
--
David Kastrup
___
bug-lilypond mailing list
b
Vik Reykja writes:
> On Sun, Sep 22, 2013 at 8:31 PM, David Kastrup wrote:
>> >
>> > programming error: no solution found for Bezier intersection
>> > continuing, cross fingers
>> >
>> > in my actual file.
>>
>> Unlikely.
gs: LilyPond will likely obey them in future even if
it ever gains the intelligence to come to the same conclusion all by
itself.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
dvantages.
A small net win is still a win, and typography is concerned with a lot
of small net wins. I doubt we'll spend a lot of energy on this one in
the near future, but that does not mean that there are cases where such
a consideration would not have benefits.
--
David Kastrup
evel/2008-08/msg00206.html
That sounds like an unrobust solution as it depends on a particular
erroneous behavior. It's quite likely that this will not work
identically across several versions of Texinfo (Texinfo 5.0 may be
different) and across d
cidentals (those have always been overlooked, I
guess).
Bug squad, can you file the original report and the examples? And can
people who have some version of 2.17 installed narrow this in some more?
I don't really fancy bisecting all the way from 2.16.
--
David Kastrup
__
David Kastrup writes:
> Gilberto Agostinho writes:
>
>>
>> I think I found two possible bugs when dealing with Automatic note
>> splitting.
>>
>> 1) when a note has an accidental and it has to be split, the ligaturas look
>> out of place.
>&
"Phil Holmes" writes:
>> Bug squad, can you file the original report and the examples? And can
>> people who have some version of 2.17 installed narrow this in some more?
>> I don't really fancy bisecting all the way from 2.16.
>>
>> --
>> Dav
David Kastrup writes:
> "Phil Holmes" writes:
>
>>> Bug squad, can you file the original report and the examples? And can
>>> people who have some version of 2.17 installed narrow this in some more?
>>> I don't really fancy bisecting all
>> people who have some version of 2.17 installed narrow this in some more?
>> I don't really fancy bisecting all the way from 2.16.
>>
>> --
>> David Kastrup
>
> It was between 2.17.4 and 2.17.9 - I don't have the intervening
> versions installe
Carl Witthoft writes:
> For christsake lose that idiotic "Top post filter" will you?
> Latest stable LilyPond, trying to compile the example file.
> OSX 10.6.8 on iMac IntelCore2Duo.
Which example file?
--
David Kastrup
___
b
't you just write
% version "2.17.23"
if you intend the header to be only for a human?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
t doing the comparably simple paste-over-the-symptoms "fix"
that masks an initialization only happening sometimes.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
tered:"
Probably. Since the example explicitly starts with a redundant
\balloonLengthOff, it would appear that either this was not always the
default, or that the documentation writer was confused.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
René Brandenburger writes:
> Hi,
>
> the following snippets crashes lilypond 2.17.26 on windows7 64bit,
>
> \version "2.17.26"
>
> \times 2/3 {s8\> s8\< s8\!}
http://code.google.com/p/lilypond/issues/detail?id=3551>
Fixed in 2.17.27. Keith
to do. Note that if you
write
\removeWithTag #'current d'4 -\tag #'current ^\markup "Hi"
then the tagged superscript still makes it into the expression that
\removeWithTag oversees. But for the use you want, you'll have to write
\removeWithTag #'correct { ... }
nam
>
> Parsing...
> [...] error: GUILE signaled an error for the expression beginning here
This issue has been entered as
http://code.google.com/p/lilypond/issues/detail?id=3624> and there
is already a patch proposed.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
apter *2.3 Command line options for convert-ly*
This is usually assumed to be common knowledge, but of course it's
"common knowledge" mostly with people accustomed to Unix.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Eluze writes:
> David Kastrup wrote
>> Eluze <
>
>> eluzew@
>
>> > writes:
>>
>>> (sorry I can't remember exactly where that was) I tried a new patch to
>>> get
>>> rid of these numerous backups:
>>>
>>> -k
Eluze writes:
> David Kastrup wrote
>> Eluze <
>
>> eluzew@
>
>> > writes:
>>
>>> David Kastrup wrote
>>
>> And then I would be afraid that it would do something besides cleaning
>> up the backups, some conversion or so. When
{ la2:
> dim }
>
> Note that
>
> toto = { la2 }
>
> works !
Not really (it's a single note, not a chord).
Try
toto = \chordmode { la2:dim }
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Michel Lemaitre writes:
> Thank you David for your quick answer and sorry for the trouble
That one was not really a lot of trouble.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/
triggered:
I'm having a weird time with that report. \\ is called a Voice
separator, so it separates voices.
Why is this problematic?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Valentin Villenave writes:
> On Thu, Oct 31, 2013 at 6:39 AM, David Kastrup wrote:
>> I'm having a weird time with that report. \\ is called a Voice
>> separator, so it separates voices.
>
> Well, yes :-)
> But for example, if you put \\ in a DrumStaff context, it
Valentin Villenave writes:
> On Thu, Oct 31, 2013 at 12:24 PM, David Kastrup wrote:
>> But you did not put \\ in a DynamicsStaff context, so it has no suitable
>> container where it could place separate Dynamics contexts.
>
> Something like that?
>
> \layout {
Valentin Villenave writes:
> On Thu, Oct 31, 2013 at 12:24 PM, David Kastrup wrote:
>> First you have to figure out what you want to happen here. Do you want
>> two Dynamics contexts with different orientation and settings? In that
>> case, you'll need to provide a s
lem:
2.14 is dead. We are not making any more releases of it.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Vik Reykja writes:
> On Sun, Sep 22, 2013 at 8:31 PM, David Kastrup wrote:
>
>> Vik Reykja writes:
>>
>> > On Sun, Sep 22, 2013 at 6:39 PM, David Kastrup wrote:
>> >
>> >> David Kastrup writes:
>> >>
>> >> Thanks for
work: which version did
this work with? Did you run convert-ly for upgrading your source file
to a newer version?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
roblem with a smaller
score than that, there is not much we can do.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
to infinite loops for some cases, and so was junked in
favor of a simpler patch by Keith) would make a difference here.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
201 - 300 of 1554 matches
Mail list logo
