;origin" is. Usually it's a repository
name rather than a branch, but maybe you have "origin" as the head of your
current/working branch too?
Anyway, I *think* your rebase command should perhaps just be
"git rebase -i origin/stable/2.20"
Interesting! Git is a confus
Not within Frescobaldi...
On 5 Nov 2017 11:38, "Phil Holmes" wrote:
> - Original Message - From: "Chris Yate"
> To: "Thomas Morley"
> Cc: "David Kastrup" ; "lilypond-devel" <
> lilypond-devel@gnu.org>
> Sent: Fri
n "assert", but is anyone planning to look at this
issue?
On Sat, 7 Jan 2017 at 18:50 Chris Yate wrote:
> On Fri, 6 Jan 2017 at 12:41 Chris Yate wrote:
>
>> On Fri, 6 Jan 2017 at 12:23 Thomas Morley
>> wrote:
>>
>> 2017-01-06 13:10 GMT+01:00 Chris Yate :
&g
On Fri, 6 Jan 2017 at 12:41 Chris Yate wrote:
> On Fri, 6 Jan 2017 at 12:23 Thomas Morley
> wrote:
>
> 2017-01-06 13:10 GMT+01:00 Chris Yate :
>
> >
> > Curiously, this didn't fail with assertions. I've just upgraded to
> 2.19.54,
> > and the t
On Fri, 6 Jan 2017 at 12:31 David Kastrup wrote:
Chris Yate writes:
> On Fri, 6 Jan 2017 at 11:34 David Kastrup wrote:
>
>>
>> Assertions should not be used when LilyPond has a sane way to continue:
>> for that case, programming errors are more appropriate. The questi
On Fri, 6 Jan 2017 at 12:23 Thomas Morley wrote:
> 2017-01-06 13:10 GMT+01:00 Chris Yate :
>
> >
> > Curiously, this didn't fail with assertions. I've just upgraded to
> 2.19.54,
> > and the test cases that crashed for me previously still crash :)
> &g
On Fri, 6 Jan 2017 at 10:23 Thomas Morley wrote:
> 2017-01-04 16:01 GMT+01:00 Chris Yate :
> > On Wed, 4 Jan 2017 at 14:25 Thomas Morley
> wrote:
>
> > Well, it's odd. I'm not sure this is anything to do with
> /overrideProperty.
> >
> > Referrin
bad, because I can't
get past the program termination. Though I would in general agree; and
moreover I wouldn't expect a 'Release' build to have assertions enabled.
But this is alerting us to something that **Should not happen** at runtime,
and ignor
On Wed, 4 Jan 2017 at 14:25 Thomas Morley wrote:
> 2017-01-04 14:26 GMT+01:00 Chris Yate :
> >
> > On Wed, 4 Jan 2017 at 12:39 Thomas Morley
> wrote:
> >>
> >> 2017-01-04 11:11 GMT+01:00 Chris Yate :
> >>
> >> > I'm not quite sur
On Wed, 4 Jan 2017 at 12:39 Thomas Morley wrote:
> 2017-01-04 11:11 GMT+01:00 Chris Yate :
>
> > I'm not quite sure what you want me to test, but, here's what I've tried.
> [...]
>
> Hi Chris,
>
> sorry not been clear enough.
> Many thanks for y
On Tue, 3 Jan 2017 at 22:58 Thomas Morley wrote:
> 2017-01-03 18:04 GMT+01:00 Chris Yate :
> > On Tue, 3 Jan 2017 at 16:23 Thomas Morley
> wrote:
>
> >>
> >> Do you have the same problems, while putting it in \layout and using
> >> manual breaks? Like:
On Tue, 3 Jan 2017 at 16:23 Thomas Morley wrote:
> 2017-01-03 17:10 GMT+01:00 Chris Yate :
> >
> >
> > On Tue, 3 Jan 2017 at 16:03 Thomas Morley
> wrote:
> >>
> >> This replies to
> >> http://lists.gnu.org/archive/html/lilypond-devel/2017-01
On Tue, 3 Jan 2017 at 16:03 Thomas Morley wrote:
> This replies to
> http://lists.gnu.org/archive/html/lilypond-devel/2017-01/msg00010.html
>
> 2017-01-03 12:23 GMT+01:00 Chris Yate :
> >
> > Hmm. No, agreed, not ready for release yet. This one prevents me using
>
is simply not working for me. I don't really have the time to investigate
the Lilypond bug (which I have motivation to do), so I really don't have
time to investigate why Gub isn't working (which I really don't have
motivation for).
I've given up trying to make an instrument
r executes in a C++ process anyway, so it'd
probably be feasible to run the tests through that in some way.
Though this approach also typically relies on the ability to inject mock
objects/services into the subject code to stub out filesystem access etc.
This might be a problem, I don't k
nctions
tend to manipulate "Grob" objects; would the tests be examining their
properties after the function call?
But what about Scheme code?...
Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
nload
(and build) some dependency. There's a lot of them and if download fails
from some flaky source site, gub fails.
Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Interesting, but perhaps not a surprise, since a Cygwin build is probably
rather closer to running on native Linux than mingw. Back to the drawing
board, I think...
Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
an certainly run this in gdb, and the
breakpoint happens on the assertion. However, the builds I have access to
don't have debugging symbols, so the backtrace isn't likely to be very
helpful.
Are there some instrumented builds available?
Chris
___
either warrant fixing if they occur.
>
> --
> David Kastrup
>
Hi David,
That's pretty interesting. The issue might have been around for years...
Were assertions ever enabled in builds previous to 2.19.21?
Chris
___
lilypond-devel mailing list
On Sat, 1 Oct 2016 at 12:50 Chris Yate wrote:
> On Sat, 1 Oct 2016 at 12:27 Phil Holmes wrote:
>
> Have you narrowed the problem down to a specific new release? - e.g. it
> happens in 2.19.32 but not 2.19.31?
>
>
> Right. Very good point.
>
> I've started agai
"make bootstrap". Perhaps this will work better
than last time. In the meantime, a binary search of 2.19 to find when this
error starts happening.
Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ate a reliable "minimal" example for this. It
only seems to happen in reasonably complicated scores with 10+ staves and a
few pages. In any case, unless I can compile this for Windows I wouldn't
be able to investigate the problem at all.
Thanks in advance!
Chris
_
> Yes, I am top-posting
I notice that issue 786 was just marked as critical. I sent the
following message to -devel four weeks ago but never received a
response. I'd appreciate advice on how to write messages that are more
responder-friendly.
Chris Snyder wrote:
Issue 786, which wa
d back in March in a
way that would allow us to revert that part of the Extender_engraver to
the way it was before my original patch. Before I try to learn how the
parser works, does this seem like an acceptable approach?
Thanks,
-Chris
___
P. In the worst outcome - my fading away
after contributing nothing other than another list of TODO's (not going
to happen, but I understand that you don't know me well enough to
believe me) - nothing will have been lost, and no Jan- or Han-Wen-hours
- LP's most valuable assets -
Valentin Villenave wrote:
May I suggest using the existing tracker on bugs.lilynet.net?
That would be excellent. Thanks.
-Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
e
know.
I'll wait for official guidance before proceeding.
-Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
nd is
deadlocked.
You're approaching this as if it's a technical issue. As of now, it's
not. I don't have the standing in the community to resolve the social
issues that must be dealt with first.
As an aside, there is a Windows binary available for download from the
as
that,
as Bertalan says, "Someone, a lead architect should decide upon rules."
I feel I'm already being pretentious - imagine me trying to tell Han-Wen
and Jan how to format their whitespace.
Again agreeing with Bertalan, I think we need some fascism here. I don't
see how this w
me assure you that the former
paragraph was written with tongue firmly implanted in cheek)
Thanks, and sorry for taking up everyone's time.
-Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
astyle still be an improvement over
the current situation? It wouldn't prevent future formatting mistakes
and it wouldn't help with the Scheme and ly code, but it would still be
a step in the right direction.
Thanks,
-Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Any takers?
-Chris
--
Chris Snyder
Adoro Music Publishing
1-616-828-4436 x800
http://www.adoromusicpub.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
u do, you may find some more
specific questions to ask. Please feel free to come back with any further
questions."
Unfortunately, this is often abbreviated as "Our entry point is in
main() (lily/main.cc)..." - I'm thankful that verbiage has not been
carried ov
m still hanging around, however, is a testament
more to the quality of the product than to any welcoming atmosphere in
the community.
(sorry if this message doesn't thread well - I couldn't figure out a
good place in the conver
for
> leaving melisma_busy as-is and modifying the call site.
I've worked out a solution that seems to work. It's now included in my
Rietveld issue for bug 786.
-Chris
Chris Snyder
Adoro Music Publishing
1-616-828-4436 x800
http://www.adoromusicpub.com
For solution #2, I meant that we can add a check in
Extender_engraver::stop_translation_timestep to see if we're in the
middle of a note, in addition to the melisma_busy() call (since
melisma_busy() doesn't currently do such a check).
Chris Snyder
Adoro Music Publishing
1
to address this:
1) Change melisma_busy() to return true if in the middle of a note
2) Alternatively, add the check in
Extender_engraver::stop_translation_timestep instead
Any guidance on which approach is preferable? Thanks.
--
Chris Snyder
Adoro Music Publishing
1-616-828-4436 x800
http://w
Carl Sorensen wrote:
> Way back in January (10 months ago!!!), Chris Snyder was working on
a patch
> for spanned arpeggios.
>
> <http://thread.gmane.org/gmane.comp.gnu.lilypond.devel/19682>
>
> I was asked to shepherd this process, but I have apparently dropped
>
al.ly?
>
> I've just run a regression test check and there's a missing hyphen
> following "Ky", though the melisma is correct (see attached image).
I'm working on it; I fixed the hyphen issue, but now there are a bunch
of other lyrics that are spaced wrong. I'l
note? Or in other words, does the processing of "_"
> rely on the code above or not.
>
> And then there is the Lyric_combine_music_iterator::start_new_syllable
> function. would that still work?
I thought of another potential problem: Does melisma_busy know about
Lyrics cont
roblem
further, but need some guidance as to where I should be looking - should
melisma_busy() know about the melisma being extended with underscores in
the lyrics, or should an additional check be added in the extender engraver?
Thanks,
Chris
--
Chris Snyder
Adoro Music Publishi
melisma. Since single
underscores extend the melisma ("You can define melismata entirely in
the lyrics, by entering _ for every extra note that has to be added to
the melisma." --LNR 2.1.3), the fix would therefore be to alter the
behavior of the melisma_busy function.
Thanks,
-Chris
--
ther.
Any feedback that you could give would be much appreciated.
Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Joe Neeman wrote:
> The problem IIRC is that the solution I had suggested to Chris wasn't
> acceptable (with good reason) to Han-Wen. Chris understandably doesn't
> seem too keen on throwing his work away and starting again with another
> idea of mine.
Part of the reason I h
e code shortly; I agree that it should be get_object.
I changed the get_object calls to get_property because the accidental-grob
callback I added to notehead to return the correct accidental grob wasn't
being called. What is the difference between objects and properties,
anyways?
Thanks,
-Chris
ing calculations done to them. Everything worked fine once I
told the correct accidentals to commit suicide and announced the copied
accidentals properly.
Thanks,
-Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Joe Neeman wrote:
> On Thu, 2009-03-26 at 10:26 -0400, Chris Snyder wrote:
>> Joe Neeman wrote:
> It's not necessary to announce every grob (for example, of the three
> copies of every breakable grob, only the middle-of-line copy gets
> announced). The code for creating th
is is because the cloned grob was never announced. Perhaps
I should modify accidental-engraver as well, and have it create two
copies there, passing them both to Accidental_placement::add_accidental?
Which copy of the accidental should be put into the accidental
Last month I sent a patch to the list dealing with lyric extenders.
Since it seems to have gotten lost in the deluge of list traffic, I'm
re-sending it, this time posting it on Rietveld:
http://codereview.appspot.com/28052
Thanks,
-
g the v2.13 directory?
-Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
t this patch fixes that instance
as well.
Thanks. I look forward to any comments.
-Chris Snyder
>From ae36a3f6e79ce3a15d4e254a8919108b9feed440 Mon Sep 17 00:00:00 2001
From: Chris Snyder
Date: Tue, 24 Feb 2009 13:02:17 -0500
Subject: [PATCH] Fix lyric extenders to end properly when there are no
uld two (or more) spanned arpeggios
be differentiated, so that the engraver would know which ones to connect
to which? There'd need to be some kind of syntax to specify which
spanned-arpeggio an individual arpeggio belongs to.
-Chris
___
lilypond-dev
Carl D. Sorensen wrote:
> Sounds to me like we have a winner. Chris, will you take on this task? I
> think you'll find that the people on -devel are happy to answer coding
> questions. Everybody wants more people who can fix/modify LilyPond code, so
> we're all happy to h
did recognize when I was making
the patch) is a non-issue - LilyPond should not be expected to produce
sensible output from non-sensible input, such as a spanned arpeggio
comprised of arpeggios of different styles. I think that throwing up a
warning would be the most desirable outcome.
Thanks.
-Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
evaluating
patches, and I appreciate the excellent-quality code that results.
Thanks for your time.
-Chris
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
he solution lies in the documentation: how about adding
information on altering spanned arpeggios using explicit \override's
instead of the macros? If that sounds like a good plan, I'm willing to
write the necessary instructions and examples.
-Chris
__
On December 20, 2008, Chris Snyder wrote:
> I did realize that the ly_symbol2scm call was not needed. I've
> attached a new patch that does not include it.
Is there any chance of my patch being accepted into master? What can I
do to make the process easier? Thanks.
-C
ymbol2scm call was not needed. I've attached
a new patch that does not include it.
Thanks.
-Chris
>From 327618ff4ee5e1e275dfb461aa325510e3f21c97 Mon Sep 17 00:00:00 2001
From: Chris Snyder
Date: Sat, 20 Dec 2008 15:14:44 -0500
Subject: [PATCH] Altered spanned arpeggios to inherit the stencil
e line of code - quite
the result after hours of work), but the functionality seems quite
elegant.
I've attached the patch according (I hope) to the standards set forth on
the LilyPond web site. Feedback (both code- and process-wise) would be
greatly appreciated. Thank you.
--
Chris Snyd
On Mac OS X 10.4.11 x86 double-clicking on the app does nothing.
Launching the binary from the command line directly gives:
~ $ ./Desktop/LilyPond.app/Contents/MacOS/LilyPond
Bus error
Chris
Han-Wen Nienhuys wrote:
See
http://lilypond.org/~hanwen/lilypad.tar.bz2
this does not include
During the course of engraving a fairly complex choral piece, I've run
into quite a few slur bugs, including 307 (slur collision with tuplet
bracket) and 379/586 (slur issues across line breaks).
Hoping to be able to fix some of the issues myself and learn about the
internals of LilyPond, I st
first published before 1923
to ensure that it is out of copyright in the USA. See the Wikipedia
Public Domain page for more info:
http://en.wikipedia.org/wiki/Public_Domain
Regards,
Chris
--
Chris Sawer - [EMAIL PROTECTED] - Mutopia team leader
Free sheet music for all at: http
Hope this is useful to somebody.
Thanks for all your effort with LilyPond.
Regards,
Chris
--
Chris Lamb, Leamington Spa, UK [EMAIL PROTECTED]
WWW: www.chris-lamb.co.uk GPG: 0x634F9A20
signature.asc
Description: This is a digi
atement is indeed correct.
Or should we be using a different unicode->bytes layout scheme?
I should have thought that UTF-8 is the ideal choice for LilyPond input
files, as it allows the whole Unicode character set to be used, while
retaining compatibility with ASCII for ease of transition.
Chris
-
n, and I will be interested to see how he gets on.
You're welcome to send the corrected 1.6 syntax file to me, and I will see if
I can update it (seeing as it was me that typeset it in the first place!).
The LilyPond developers may be interested in seeing what the problem with
convert-ly is.
C
owever, and
the results in some cases can be unexpected.
If you want to find files on Mutopia that match the version of LilyPond you
have installed, you can use the 'Advanced Search' page to specify a
particular version (eg. 2.2).
Chris
--
Chris Sawer: [EMAIL PR
Jan Nieuwenhuizen wrote:
> Chris Jackson writes:
>
>> Is this restriction to files and directories without spaces really an
>> insurmountable problem?
>
> Yes, sort of. Tex cannot handle file names with spaces.
Ouch, I didn't realise that! But it can run inside *di
For better or worse,
default directories with spaces are here to stay on Windows. If we start to
recommend Jérémie's clickable-ly script as the way for newbies to run lily,
then it'd be nice if ly files would be clickable from anywhere.
--
chris
__
ngled in the process of copying: only
the first few lines are copied over. However (say, the PDF file is called
test.pdf, and the destination directory is P:\lily) these commands both
work - the complete PDF file is copied over.
copy C:\cygwin\tmp\test.pdf %1.pdf
copy C:\cygwin\
Chris Jackson wrote:
> copy C:\cygwin\tmp\*.pdf %1.pdf
>
> With this command, my PDF file is mangled in the process of copying:
> only the first few lines are copied over.
Found a solution to this problem now, after a quick google. If you specify
copy /B C:\cygwin\tmp\*.pdf %1.p
British (and Canadian I guess) spelling, and
"esthetics" the American, but I agree we should be consistent here. I think
the British version sounds more, um, beautiful :)
--
chris
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
gram to edit the text in, another program to
compile the .ly, and a *third* program to view the output. People expect to
just click an icon, and live inside one app that does everything they want.
--
chris
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
built in. I've no concept how much work it
would to take to implement such a beast though (other than "bloody loads").
--
chris
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
? Alternatively, or perhaps as
well, should the default margins be changed?
Again, thanks to everyone, but especially Han-Wen and Jan, for all the work
they've done to LilyPond. Its rapid growth never ceases to amaze me!
Chris
--
Chris Sawer - [EMAIL PROTECTED] -
than I would have expected. So I'm
> perfectly willing to get more stuff from unstable, but I don't know
> what.
It doesn't seem to be just a Debian problem: I get a very similar error when
trying to compile Lily 1.7.27 or 1.7.28 on Mandrake 8 (much upgraded):
make[2]: Leaving
- Original Message -
From: "Jan Nieuwenhuizen" <[EMAIL PROTECTED]>
> "Chris Jackson" <[EMAIL PROTECTED]> writes:
>
> > Just having fun trying to build the current development version 1.7.21
on
> > Cygwin. I've managed to compile it
, and doesn't crash when
the octaviation statements are in the right hand.
--
Chris
\version "1.7.21"
righthand = \notes \relative c'' {
#(set-octavation 1)
<> <> <> <> <>
#(set-octavation 0)
}
lefthand = \notes \relative c' \con
ure how the python script
might be changed.
--
Chris
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
for Mutopia, as it removed
the need to mess around with the Gimp.
What would be even better is if one of these images was produced for each
"section" of the .ly file (I'm not sure of the proper name for these
sections), in the same way that a MIDI file is produced for each section. I
own).
Applying it before the "e1" doesn't make any difference to the second
bracket,
as the bracket has already been created (with the second \sostenutoDown)
before the property is applied.
It's the default to not include the final note, as (IMO) this represents
#'(0.0 . -3.0)
[ e16 \arpeggio e e
\property Staff.Arpeggio \override #'direction = #1
e \arpeggio ]
}
}
--
chris
Index: ChangeLog
===
RCS file: /home/lilypond/lilypond/ChangeLog,v
retrieving re
Hi,
This patch will fix the pedal line-lengths bug. Sorry this wasn't sent
sooner..
--
chris
Index: ChangeLog
===
RCS file: /home/lilypond/lilypond/ChangeLog,v
retrieving revision 1.235
diff -p -u -r1.235 Chan
hin LilyPond (using ly2dvi rather than
lilypond-book), then we'd be very grateful.
I've CCed this to Erik Sandberg who has also expressed an interest in having
footnotes in LilyPond to see if he has anything extra to add (I'm not sure if
he's on any of the LilyPond mailing lists).
something along the
lines of the LaTeX footnote feature - maybe even using it, since LilyPond
uses LaTeX?
Thanks,
Chris
--
Chris Sawer - [EMAIL PROTECTED] - Mutopia Maintainer
Free sheet music for all at Mutopia: http://www.mutopiaproject.org
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
On Tue, Apr 16, 2002 at 10:01:12PM +0200, Rune Zedeler wrote:
> Chris Jackson wrote:
>
> >Because they're recognised by the syntax table, and don't need a
> >multi-line regexp to match them. As they should in lilypond...
>
> How comes that c++ comments are ea
regexp to match them. As they should in lilypond...
Shit - the syntax table is wrong. Looks like I broke the multi-line
comments highlighting with a stupid typo (in the bracket-blinking patch).
Sorry about that. Fix attached.
--
chris
Index: lilypond-font-lock.el
=
mean to tie grace notes? I don't
> think I've ever seen it.
When the second note is a chord, it's needed to indicate a sort
of half-arpeggio, e.g.
\grace a8 ~
or something like
\grace {a8 ~ ~ }
--
chris
___
Lilypond-devel mailing
On Wed, Apr 10, 2002 at 02:25:57PM +0200, Rune Zedeler wrote:
> Chris Jackson wrote:
>
> > What's happening with rests at the moment? r4 currently gives
> > an r8, and r8 gives a classical r4 (a reflected r8).
>
> You haven't uninstalled the old fonts corr
ngs - they're a PITA when reading
music!
--
chris
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
David Raleigh Arnold <[EMAIL PROTECTED]> wrote:
> Chris Jackson wrote:
> > Before I get bored of hacking brackets, I'd like to implementvertical
> > brackets down the side of chords, meaning "don't arpeggiate me". I
>
> Germans have been using th
://mail.gnu.org/pipermail/bug-lilypond/2001-September/49.html>?
Running that example now gives two high brackets, should these be low?
--
chris
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
if you can do it by simply overriding the brew-molecule
> function, then all other logic can be left unchanged.
OK, that works fine, here's the patch!
cheers,
--
chris
Index: ChangeLog
===
RCS file: /home/lilypond/lilypon
On Tue, Apr 09, 2002 at 08:13:26PM +0200, Rune Zedeler wrote:
> Quoting Chris Jackson <[EMAIL PROTECTED]>:
>
> > Before I get bored of hacking brackets, I'd like to implement vertical
> > brackets down the side of chords, meaning "don't arpeggiate me&qu
This fixes a silly bug in Emacs indentation (open new .ly file,
type \score { , and get an error message)
--
chris
Index: ChangeLog
===
RCS file: /home/lilypond/lilypond/ChangeLog,v
retrieving revision 1.62
diff -p -u -r1.62
called (Arpeggio, or a new one,
ChordBracket?) and what property should be set to turn it on? Something
like \property Staff.Arpeggio \override #'arpeggio-type = #'bracket ?,
and then use ordinary \arpeggio requests?
--
chris
___
Lily
the tuplet indicator is in a very strange place for some shapes of
beam.
--
chris
Index: input/test/tuplet.ly
===
RCS file: /home/lilypond/lilypond/input/test/tuplet.ly,v
retrieving revision 1.11
diff -p -u -r1.11 tuplet.ly
--- input/test
you mean about Text_spanner::brew_molecule being too long
and hairy. I'll try and think how to split it up.
--
chris
Index: lily/piano-pedal-engraver.cc
===
RCS file: /home/lilypond/lilypond/lily/piano-pedal-engraver.cc,v
retrieving revi
ow-paren-mode'
(which highlights the paren pair when you move the cursor over one of
them) yet.
The patch was made using cvs diff, hope it applies OK!
--
chris
Index: ChangeLog
===
RCS file: /home/lilypond/lilypond/ChangeLog,v
retrie
y got any ideas what's causing this?
--
chris
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
1 - 100 of 116 matches
Mail list logo
