happens with your copyright for your LilyPond version? Have you
signed it away? Do you retain publishing rights for it?
Strauss died in 1949 so copyright of his heirs will stick around until
something like 2019 I think. But if you were free to publish it
afterwards, that would be great.
--
David
\alias Voice
\override NoteHead.color = #blue
}
}
\accept-like-layout Voice myVoice
An extra command seems like bikeshedding when you can just write
\accept-like Voice myVoice \layout { }
instead.
--
David Kastrup
___
bug-lilypond
Paul Morris p...@paulwmorris.com writes:
David Kastrup wrote
An extra command seems like bikeshedding when you can just write
\accept-like Voice myVoice \layout { }
instead.
Good point! Lets just go with that.
Actually, that kind of usage only works outside of \score.
If you write
Dan Eble d...@faithful.be writes:
\version 2.19.16
\score {
\partcombine
\relative { c''1 | }
\relative { a'2. f4 }
}
That's issue 100
URL:https://code.google.com/p/lilypond/issues/detail?id=100.
--
David Kastrup
___
bug-lilypond
block as their lyrics. Or something like that (if they are not
accompanied by any non-associated context in the I think that's
also ok).
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug
, LilyPond is allowed to
choose tie directions in spite of the voice crossing.
Usually you'd want to have the higher pitched voice first _unless_ you
need to have a visual inversion (like when alto II dips below alto I).
--
David Kastrup
___
bug-lilypond mailing
Trevor Daniels t.dani...@treda.co.uk writes:
David Kastrup wrote Saturday, March 14, 2015 7:28 AM
Trevor Daniels t.dani...@treda.co.uk writes:
I've just noticed that the examples of using the built-in template,
satb.ly, in the Learning Manual, see
http://www.lilypond.org/doc/v2.19
Dan Eble d...@faithful.be writes:
David Kastrup dak at gnu.org writes:
\voiceOne / \voiceTwo imply tie directions. If you write
[...]
instead (which uses \voiceOne and \voiceTwo internally) you'll get the
same output above and below. In your example, LilyPond is allowed to
choose tie
=0x8734cc0) at score.cc:141
and the rest is not really interesting.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
has managed tieing Scheme
into its input language a lot more smoothly than LuaTeX did with Lua.
As opposed to TeX/LaTeX, LilyPond itself has a proper grammar. Mostly.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
by default. And there is nothing else.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Simon Albrecht simon.albre...@mail.de writes:
Am 05.03.2015 um 12:58 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Hello list,
I use a music function to tweak the X and Y-offsets for a grob. This
function used to work in 2.19.8, but in 2.19.15 and .16 it just
case: those may change
behavior in some future version.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
://code.google.com/p/lilypond/issues/detail?id=4036,
URL:https://code.google.com/p/lilypond/issues/detail?id=4022.
If you have additional suggestions to make, they probably would pick up
starting with one of those reports.
--
David Kastrup
___
bug-lilypond
system. The LilyPond version is by far the
most important information: be sure to include it in any question.
It can be sort-of implied by putting an appropriate \version command in
your minimal example URL:http://www.lilypond.org/tiny-examples.html.
All the best
--
David Kastrup
problem. Maybe because GCC is written
in C++ these days.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
there.
I'll try taking a look later this day. But for the future you'll
improve your chances for competent replies by making it really easy to
get a first impression of the bug.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
}
}
}
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
is not
loaded. For the record, my ~/.guile looks like
(use-modules (ice-9 readline))
(activate-readline)
So maybe we should instead advertise
(format #t ~a\n a)
here? Or put a (begin ...) around this example?
--
David Kastrup
___
bug-lilypond mailing
pls p.l.schm...@gmx.de writes:
On 26.04.2015, at 11:20, David Kastrup d...@gnu.org wrote:
But when I try this in the scheme sandbox (LilyPond v2.19.15) on
Ubuntu 14.10 (and Mac OS 10.9.5) I get:
So it is
likely a REPL feature of Guile-1.8 when the readline library is not
loaded
code).
Apart from that, it's a pretty good crutch...
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
-music-function (parser location music)(ly:music?)
(make-relative (music) #{ $music $music #}))
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Simon Albrecht simon.albre...@mail.de writes:
Am 25.04.2015 um 13:17 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Hello,
as Harm has pointed out, the following example gives unexpected
(i.e. different) output:
\version 2.19
repeat-note =
#(define-music-function
gega.c
dak@lola:/tmp$ ls -l gega.o
-rw-rw-r-- 1 dak dak 0 May 1 16:46 gega.o
No. It is a safe bet that there _are_ intermediate files, but they'll
likely end up somewhere on /tmp or similar.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond
.
There is a big difference: If you compile a .c file, the .o files
stays by default; the compiler doesn't remove it.
Uh, wrong?
cd /tmp;echo main(){return 0;} gega.c;gcc -o gega gega.c;ls gega*
gega gega.c
--
David Kastrup
___
bug-lilypond mailing
that
remove intermediate files.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
quite a bit about
PostScript to make use of the \postscript markup in LilyPond.
Not sure yet.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
to demonstrate that skipTypesetting, when activated, causes a
problem. At least that's what I think this should demonstrate.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
in
the archives.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
:
http://lilypond.org/doc/v2.19/Documentation/notation/the-articulate-script
It's also sort of insane. Shouldn't we rather fix this?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Federico Bruni f...@inventati.org writes:
Il giorno lun 11 mag 2015 alle 17:15, David Kastrup d...@gnu.org ha
scritto:
Your bug summission page is very rude and annoying.
We don't have a bug submission page: users are advised to mail
problem
reports to this bug list. I have no idea what
Dan Eble d...@faithful.be writes:
David Kastrup dak at gnu.org writes:
Dan Eble dan at faithful.be writes:
So what do you expect for
{ \hide c'' e''4 }
Stem or no stem?
Good question. In that context, hiding just the head would not surprise me.
But then what about {\hide c''4
the safer choice.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
the Stem (since its cause points to the c'' NoteHead) while
{ c'' \single\hide Stem g''4 }
doesn't hide it (since its cause points to the c'' NoteHead).
So it's somewhat tricky to derive a consistent behavior here.
--
David Kastrup
___
bug-lilypond
would actually get closer to
the writer's actual musical intent?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ArnoldTheresius arnold.we...@siemens.com writes:
David Kastrup wrote
...
Why are you removing the Vertical_align_engraver ?
the original question at the German Lilypond user forum was:
Is there a *better method than this dirty removal of the
Vertical_align_engraver* to align vertically two
[ and ]? That does not seem like an improvement.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
have similar cases elsewhere) and leave the more invasive
change for proper review/discussion for later.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
to have complained about the non-minimality of the
example since the book appears entirely unnecessary.
But indeed without the book, only a warning (with a ludicrous error
location) occurs. It is interesting that the behavior of normal score
and book differ in that respect.
--
David Kastrup
Phil Holmes m...@philholmes.net writes:
David Kastrup d...@gnu.org wrote in message
news:871tgott5d@fencepost.gnu.org...
I have to admit that I'm leaning towards the last solution. However, we
have had a few regressions in 2.19.22. If Phil was thinking about
rolling 2.19.23
every \chordmode by \transpose c c' \chordmode but you
are not going to make anybody happy with that.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
.
If this is not a bug, I'd appreciate learning what's
wrong with what I'm trying to do.
You are setting alignBelowContext too late.
Try \context Lyrics = lyricsI \with { alignBelowContext = upper }
\lyricsto ...
--
David Kastrup
___
bug-lilypond
and the controlling
context being in the same ... construct. Clearly that
assumption/requirement is not met too often for comfort.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
pls p.l.schm...@gmx.de writes:
On 23.05.2015, at 16:57, David Kastrup d...@gnu.org wrote:
pls p.l.schm...@gmx.de writes:
Hi all,
here’s another issue I posted somewhere and Carl answered:
P.P.S.: On a different note: some day I would like to get to know the
reason why in \chordmode
a patch that would appear to fix the problem but I'm somewhat
leery to propose it since I don't understand why the patch would not be
needed in general rather than just for the starts-with-c' situation.
--
David Kastrup
___
bug-lilypond mailing list
bug
{
\clef bass
}
}
Note that I'm not using \new Staff ... here in order not to create a
staff competing with the one delivered by \autochange, but rather
\context Staff in order to mesh with what might already be created.
--
David Kastrup
___
bug
the given example and
let it do the same, it goes down the drains as well. If you take your
example and replace the first c' with something else, it works.
Issue 4569
URL:https://code.google.com/p/lilypond/issues/detail?id=4569 should
fix that.
--
David Kastrup
seems nonsensical since it's Google Code that
is shutting down rather than Rietveld.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
be the modus
operandi when Rietveld is gone, not Google Code.
I am not involved with the setting up of the new tracker system so
don't send me questions about that, they can go to the dev-list.
Let's hope that this soon gets into a state where the interregnum can be
retired.
--
David Kastrup
/archive/html/bug-lilypond/2015-08/msg00065.html
--David Kastrup
Thanks for that. :) Now, I've added the archive to my toolbar for
future checking.
The full text follows (without HTML tags; I had used {raw}).
...
Would this be better initially discussed on 'dev'? I don't know what
for the expression beginning here
I am not really surprised that you are not successful running the
executable for LilyPond 2.16.2 with the init.ly file from LilyPond
2.18.2.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org
contents of the input
file and the version of LilyPond has.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
://lilypond.org/tiny-examples.html. It is not
clear what input you use with what expectations and what results.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
:
If you take the file ly/Welcome-to-LilyPond-MacOS.ly from a version
earlier than 2.11.65 (!) and compile it with a version later than
2.17.16 (!), the output will look one octave too low.
It would be rather important to figure out just what file and content we
are talking about.
--
David Kastrup
mail client, but you can
also save it faithfully as one file with any sane mail client.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Simon Albrecht simon.albre...@mail.de writes:
Am 24.08.2015 um 18:45 schrieb David Kastrup:
Simon Albrecht simon.albre...@mail.de writes:
Am 20.08.2015 um 09:41 schrieb Phil Holmes:
For trivially small examples (like this is) I think most people find
it far easier to comment if you post
. I can't even imagine what you'd
expect LilyPond to be doing here.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
in time.
Then he complains that LilyPond does not react to this slander in the
way he expected.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
actually sent
out on the list by looking at
URL:http://lists.gnu.org/archive/html/bug-lilypond/2015-08/msg00065.html
which is an earlier version of your mail with the same problem.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
magically is
avoided with other start notes by _starting_ with the first context
change which likely is performed by the autochange iterator _before_ any
simultaneous creation of contexts).
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond
(map-some-
music (lambda # #) (expand-repeat-chords! # music) ...):
C:/Program Files
(x86)/LilyPond-latest/usr/share/lilypond/current/scm/music-func
tions.scm:1987:3: Wrong number of arguments to #procedure map-some-music
(map?
music)
Running convert-ly -ed on the file should fix it.
--
David
David Kastrup d...@gnu.org writes:
Knute Snortum ksnor...@gmail.com writes:
LilyPond 2.19.21 will process the attached file without error but 2.19.22
prints the following:
Parsing...C:/Program Files
(x86)/LilyPond-latest/usr/share/lilypond/current/scm/
music-functions.scm:1987:3
Knute Snortum ksnor...@gmail.com writes:
On Tue, Jun 30, 2015 at 11:43 AM David Kastrup d...@gnu.org wrote:
Sorry, talked too soon. This is indeed a problem in LilyPond itself.
Will take a look.
This source file...
Parsing...C:/Program Files
(x86)/LilyPond-latest/usr/share/lilypond
helpful, maybe leading
to its underuse. Is there a good use case for the proposed behavior as
well or is this just a matter of code/doc hygiene for you?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman
and list recently!
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
accordingly.
Initial acciaccatura removed because it messed up the stem direction
in voice one and produced a warning about clashing note columns.
Note the last sentence. The respective acciaccatura has been reinstated
in the mean time.
--
David Kastrup
Thomas Spuhler thomas.spuh...@btspuhler.com writes:
On Friday, July 10, 2015 02:38:14 AM David Kastrup wrote:
Thomas Spuhler thomas.spuh...@btspuhler.com writes:
On Friday, July 10, 2015 01:43:22 AM David Kastrup wrote:
Unmodified LilyPond should not even start up due to encoding
problems
. The properties in the default Voice are
independent from the properties in Voice = 1 and Voice = 2.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
"Phil Holmes" <m...@philholmes.net> writes:
> - Original Message -----
> From: "David Kastrup" <d...@gnu.org>
>
>> Phil, this is absolutely serious stuff, likely causing crashes for large
>> scores on most platforms. Too bad we did no
2086/
Well, some basics would certainly not be amiss, yes. I'm not overly
enthused about these statistics as they tell only a small part of the
story, but then better to tell a small part rather than nothing.
--
David Kastrup
___
bug-lilypond maili
ype
bt
at the point of failure in order to get a backtrace. This will give us
more information about the context of the assertion failure and might
suggest a reasonable path forward.
Thanks
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gn
David Kastrup <d...@gnu.org> writes:
> Dan Eble <d...@faithful.be> writes:
>
>> Forgive me for being brief, but I thought I should at least mention
>> this in case someone would like to approach it with code review:
>>
>> Thread 0 Crashed:: Dispatch
ously. The force commands work until
the next force command is made unless you use a "once" form (the input
syntax has changed, but "once" is contained in one form or another in
the resulting command).
> So if you could get his attention--maybe make a donation--he could
> p
efinite changes in the last release.
So an actual input file triggering the problem would be important.
Preferably, of course, when the error would be reproducible.
Also a disassembly of Slur_proto_engraver::derived_mark() so that one
has a chance to figure out the exact instruction of th
're interested.
That looks rather messy (basically something like an invalid iterator).
I'm afraid that this one is not likely to be pinned down without an
actual minimal example since it seems to rely on a particular history of
things.
It's reproducible? Did the same file compile previously
nt
place every time.
> Guile2 is not specific to the building of the documentation as far as
> I am aware.
The documentation is complex, and LilyPond does not work on complex
scores using Guile2. It's not more than proof-of-concept quality right
now.
--
David Kastrup
e. The formatted output will likely be the same, but avoiding
an overfull source line is better style.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> Should I add an example to issue 4654 anyway?
>
> Let's put relevant info in the issue on the tracker, as I've done right now.
> I'd call the info about tablature relevant, ofcourse.
>
> Although, I don't think the bug is triggered by text (vs numbers) or
> custom defined fret-tables, see my recent post there
Ok, got it.
It's only offset-fret which does the damage?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Thomas Morley <thomasmorle...@gmail.com> writes:
> 2015-11-07 0:06 GMT+01:00 David Kastrup <d...@gnu.org>:
>>
>> Ok, got it.
>>
>> It's only offset-fret which does the damage?
>
> Just investigating offset-fret.
> At first glance the return-valu
"Phil Holmes" <m...@philholmes.net> writes:
> "David Kastrup" <d...@gnu.org> wrote in message
> news:87twpt4rx3@fencepost.gnu.org...
>
>> The LSR version of vspace (when was this ever a good idea?) by now has
>> markedly diverged from the
he built-in variant, so it really should get
removed and its effect compensated.
So it might make sense to run
convert-ly -f 2.17.18 -t 2.17.19
on the LSR snippet (though it's possible that this has already been done
once and should not be repeated) before throwing out its own vspace
definition.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
eeping track of the complex relation between this kind of
line-break related killed accidental and the following one is rather
harder to pin down since the following one needs to have no vicinity to
either tie or line break.
--
David Kastrup
___
bug-lilyp
inherited
this mess. Before \temporary, there was just "\override" which did the
same as the Scheme functions "*-set" rather than "*-override", namely
always implying pop-first = #t .
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Francisco Vila <paconet@gmail.com> writes:
> 2015-10-11 9:07 GMT+02:00 David Kastrup <d...@gnu.org>:
>> Francisco Vila <paconet@gmail.com> writes:
>>
>>> 2012/3/16 Xavier Scheuer <x.sche...@gmail.com>:
>>>
Thomas Spuhler thomas.spuh...@btspuhler.com writes:
On Friday, July 10, 2015 01:43:22 AM David Kastrup wrote:
Unmodified LilyPond should not even start up due to encoding
problems. This may depend on the actual version of GUILE 2.x
however.
I converted about 10 .ly files to pdf using
are affected
as well. If the bug has already been dealt with, there is neither
nothing to do, or you can add a comment that you encountered this bug
also and are glad for the fix.
Either way, that does not cause additional work.
--
David Kastrup
___
bug-lilypond
such as the package is
not working.
Well, the current situation for guile-2 definitely is the package is
not working. There are quite fewer impediments to is not working
than there were a year ago: there has been active work in that area.
But those that remain are not trivial.
--
David Kastrup
an unsolved problem.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Thomas Spuhler thomas.spuh...@btspuhler.com writes:
On Friday, July 10, 2015 12:42:32 AM David Kastrup wrote:
Thomas Spuhler thomas.spuh...@btspuhler.com writes:
On Friday, July 10, 2015 12:28:53 AM you wrote:
ice-9/eval.scm is a file from GUILE 2.0. LilyPond requires compilation
CollapsedStaff
\new Staff ...
\new Lyrics ...
\new ChordNames ...
seems pretty descriptive, more so than MixedStaff.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Simon Albrecht simon.albre...@mail.de writes:
Am 26.08.2015 um 18:52 schrieb David Kastrup:
New issue 4577
Status: Started
Summary: Add StaffAxis context type
Tags: Type-Enhancement Patch-new
Rietveld issue: 265730043 (https://codereview.appspot.com/265730043)
Issue description:
Add
David Kastrup d...@gnu.org writes:
David Kastrup d...@gnu.org writes:
tisimst tisimst.lilyp...@gmail.com writes:
I'm not necessarily against it being called StaffAxis, but I wonder
if something like MixedStaff is more appropriate? Just thinking out
loud. I love this idea, btw.
StaffAxis
David Kastrup d...@gnu.org writes:
tisimst tisimst.lilyp...@gmail.com writes:
I'm not necessarily against it being called StaffAxis, but I wonder
if something like MixedStaff is more appropriate? Just thinking out
loud. I love this idea, btw.
StaffAxis is as appropriate as it gets
New issue
Status: Started
Summary: Add StaffAxis context type
Tags: Type-Enhancement Patch-new
Rietveld issue: 265730043 (https://codereview.appspot.com/265730043)
Issue description:
Add StaffAxis context type See the regression test for more info.
--
David Kastrup
tisimst tisimst.lilyp...@gmail.com writes:
On 8/26/2015 1:14 PM, David Kastrup [via Lilypond] wrote:
David Kastrup [hidden email]
Perhaps OneStaff?
\oneVoice _is_ sort of the name for not separating voices vertically.
I can see that, but it still doesn't seem quite right to me. As I've
. There are a number
of uses for that, for both parallel and immediately successive contexts.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
David Kastrup d...@gnu.org writes:
Simon Albrecht simon.albre...@mail.de writes:
Am 26.08.2015 um 18:52 schrieb David Kastrup:
New issue 4577
Status: Started
Summary: Add StaffAxis context type
Tags: Type-Enhancement Patch-new
Rietveld issue: 265730043 (https://codereview.appspot.com
://lsr.di.unimi.it/LSR/Item?id=751.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Phil Holmes m...@philholmes.net writes:
David Kastrup d...@gnu.org wrote in message
Documentation/snippets/automatically-changing-the-stem-direction-of-the-middle-note-based-on-the-melody.ly
by replacing
\override Stem.neutral-direction = #'()
with
\stemNeutral
which
tisimst tisimst.lilyp...@gmail.com writes:
On 8/26/2015 4:45 PM, David Kastrup [via Lilypond] wrote:
tisimst [hidden email]
/user/SendEmail.jtp?type=nodenode=180230i=0 writes:
- CompositeStaff
- HybridStaff
- StaffBlend
- AssortedStaff
Maybe StaffAxis is the best one.
Of those
901 - 1000 of 1473 matches
Mail list logo