Status: Accepted
Owner:
Labels: Type-Documentation Priority-Medium
New issue 1221 by brownian.box: docs: Examples for \betweenLilyPondSystem
contain two '#' instead of one
http://code.google.com/p/lilypond/issues/detail?id=1221
Reported by Spela Kermelj.
On Sat 14 Aug 2010, 21:43 Spela Kermelj wrote:
Thanks, I would have never found this solution myself...
However, there's a typo in the manual, section Selected snippets, examples
2 and 4, should be
\ifnum#1...
instead of
\ifnum##1...
Thank you, added to tracker as issue 1221:
Status: Accepted
Owner:
Labels: Type-Collision Priority-Medium
New issue 1222 by brownian.box: If one fingering has up orientation, then
that what is left collides with accidental
http://code.google.com/p/lilypond/issues/detail?id=1222
Reported by Nick Payne:
% -8
On Mon 16 Aug 2010, 17:19 Nick Payne wrote:
Is this a bug or a known problem or how things are supposed to work?
If the fingering for the C# is to the left, then the fingering for
the A automatically avoids the accidental. if the fingering for the
C# is above the note, whether placed by using
On Sun 15 Aug 2010, 18:37 Sanford Lung wrote:
Upon trying to unzip lp 2.12.3 I get a dialogue that says:
Unable to unarchive lilypond-2.12.3-1.darwin-x86.tar.bz2 into
Downloads.
(Error 32 - Broken pipe.)
Help please.
Please, Sanford Lung, can you check just everything --- free space
Comment #3 on issue 1219 by brownian.box: Broken tie may become a too small
dot
http://code.google.com/p/lilypond/issues/detail?id=1219
Tie after line break is rather invisible.
To mimic that result i've set line-width to too small value, and notes
are engraved rather tight. But in real
Updates:
Labels: Patch
Comment #7 on issue 1041 by i...@hulin.org.uk: Output suffix for score
should be documented
http://code.google.com/p/lilypond/issues/detail?id=1041
I have produced a patch which is available for review on Rietveld
http://codereview.appspot.com/2004041.
Ian
Comment #19 on issue 989 by pkx1...@hotmail.com: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I think this is now done.
of the 6 remaining snippets, 4 were committed yesterday and the last 2 have
been put
Comment #1 on issue 1221 by d...@gnu.org: docs: Examples for
\betweenLilyPondSystem contain two '#' instead of one
http://code.google.com/p/lilypond/issues/detail?id=1221
Inside of macros, you need to replicate # in order to get its original
meaning. So the first definition is wrong, and
Comment #2 on issue 1221 by brownian.box: docs: Examples for
\betweenLilyPondSystem contain two '#' instead of one
http://code.google.com/p/lilypond/issues/detail?id=1221
Sorry, that was my (not Spela's) mistake.
___
bug-lilypond mailing list
Hi!
I installed Ubuntu 10.04 LTS two weeks ago in my computer. I went to the
download space (in german synaptic-paketverwaltung) and I downloaded
lilypond, but I looked for the program in my computer and I didn't find it.
Normally there's a place, where you can find all the programs that you
On Mon 16 Aug 2010, 07:56 Javi wrote:
Hi!
Hi!
I installed Ubuntu 10.04 LTS two weeks ago in my computer. I went to the
download space (in german synaptic-paketverwaltung) and I downloaded
lilypond, but I looked for the program in my computer and I didn't find it.
Normally there's a place,
Javi javid...@hotmail.com writes:
I installed Ubuntu 10.04 LTS two weeks ago in my computer. I went to
the download space (in german synaptic-paketverwaltung) and I
downloaded lilypond, but I looked for the program in my computer and I
didn't find it. Normally there's a place, where you can
Jean-Charles,
On 14/08/2010 17:09, Jean-Charles Malahieude wrote:
Hi all!
On my way to translate running.itely I notice that we have
an @example environment that runs off the page in section
LilyPond in chroot jail (starting line 509 of the source).
It is reproduce as is in the full script for
Le 16/08/2010 16:14, James disait :
Jean-Charles,
On 14/08/2010 17:09, Jean-Charles Malahieude wrote:
Hi all!
On my way to translate running.itely I notice that we have
an @example environment that runs off the page in section
LilyPond in chroot jail (starting line 509 of the source).
It is
On Mon, Aug 16, 2010 at 3:47 PM, Jean-Charles Malahieude
lily...@orange.fr wrote:
Le 16/08/2010 16:14, James disait :
Is it possible to split this script line?
Yes, I checked CG doc policy:
...if possible, use a trailing backslash to break up a single line,
indenting the next line with 2
Comment #6 on issue 612 by csny...@mvpsoft.com: spacing problem in tied
chords with accidentals
http://code.google.com/p/lilypond/issues/detail?id=612
When my patch was discussed, it seemed to me that the powers-that-be
concluded that it was the wrong approach and not worth fixing up:
Comment #20 on issue 989 by percival.music.ca: ensure that no information
about 2.12.3 features is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
LSR seems to be down; we won't have the latest 2 snippets until it's back
up and we can download from the database.
Le 16/08/2010 17:02, Graham Percival disait :
On Mon, Aug 16, 2010 at 3:47 PM, Jean-Charles Malahieude
lily...@orange.fr wrote:
Le 16/08/2010 16:14, James disait :
Is it possible to split this script line?
Yes, I checked CG doc policy:
...if possible, use a trailing backslash to break up a
Updates:
Status: Started
Owner: Carl.D.Sorensen
Comment #4 on issue 1215 by percival.music.ca: Woodwind diagrams in the NR
http://code.google.com/p/lilypond/issues/detail?id=1215
Carl said he wanted to do this.
___
bug-lilypond
Updates:
Status: Started
Owner: tdanielsmusic
Comment #6 on issue 1026 by percival.music.ca: Documentation: adapting
Lyrics when using \repeatTie
http://code.google.com/p/lilypond/issues/detail?id=1026
Trevor is rewriting the entire section, so he should take this into
Updates:
Status: Fixed
Owner: ---
Labels: fixed_2_13_31
Comment #8 on issue 1041 by percival.music.ca: Output suffix for score
should be documented
http://code.google.com/p/lilypond/issues/detail?id=1041
Pushed as 9748b8a77001b73bfd2bf35e27172a63d780c78d
Status: Started
Owner: PhilEHolmes
Labels: Type-Documentation Priority-Medium
New issue 1223 by percival.music.ca: doc for score-final mark mangles
score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=1223
issue 573:
% The score-final mark badly mangles the
Updates:
Status: Fixed
Owner: ---
Comment #13 on issue 573 by percival.music.ca: score-final mark mangles
score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
This was fixed almost two bloody years ago. The doc issue is a separate
matter, and
Updates:
Status: Fixed
Labels: fixed_2_13_31
Comment #3 on issue 1221 by percival.music.ca: docs: Examples for
\betweenLilyPondSystem contain two '#' instead of one
http://code.google.com/p/lilypond/issues/detail?id=1221
David pushed a fix in
Dear LilyPonders,
while trying to typeset some vocal music I encountered some
difficulties with \autoBeamOff:
1) \autoBeamOff has no effect on other voices when used in a global
variable/ghost voice. It has to be turned on explicitly for each
voice. This is probably intentional but AFAIK
Eluze wrote Sunday, August 15, 2010 10:20 AM
Trevor Daniels wrote:
The mingw binary of 2.13.30 gives the following error
under Vista on my system:
Running lilypond-book
Traceback (most recent call last):
File c:/program files/lilypond/usr/bin/lilypond-book.py, line
86, in ?
import
Updates:
Status: Accepted
Owner: ---
Comment #6 on issue 1129 by pnorcks: Font styles return to default when
font size changed
http://code.google.com/p/lilypond/issues/detail?id=1129
I don't really have any ideas about how to fix this at the moment.
I made a few comments in
On 8/16/10 3:30 PM, Patrick Schmidt p.l.schm...@gmx.de wrote:
Dear LilyPonders,
while trying to typeset some vocal music I encountered some
difficulties with \autoBeamOff:
1) \autoBeamOff has no effect on other voices when used in a global
variable/ghost voice. It has to be turned on
Comment #19 on issue 1096 by musiccomposition: ly:parser-parse-string
segfaults when directly called at toplevel
http://code.google.com/p/lilypond/issues/detail?id=1096
New patch to use parser_error().
Attachments:
0001-don-t-allow-ly-parser-parse-file-to-continue-unless-.patch 1.7
30 matches
Mail list logo
