noteworthy: not only the stem across the staves is not drawn, but the note
duration is also changed (or is it only the flag which gets cut away?)
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/crossStaff-breaks-if-stem-direction-changes-tp137717p137795.html
Sent
Ben Rudiak-Gould wrote
% The end of the ligature bracket is not printed
\version 2.17.8
{ \[ c'1 \break d'1 \] }
see NR
http://www.lilypond.org/doc/v2.17/Documentation/notation/ancient-notation_002d_002dcommon-features#ligatures
Known issues and warnings
Ligatures need special spacing that
On Fri, Dec 14, 2012 at 10:45:50AM +0100, Arle Lommel wrote:
(Lilypond 2.16.1)
http://lilypond.org/doc/v2.16/Documentation/notation/fonts contains
instructions on how to change default document fonts. The instructions
require hard coding a staff size of some sort. However, if the global
Ben Rudiak-Gould wrote
% The flat symbol is unreasonably far above the note
\version 2.17.8
{ \set suggestAccidentals = ##t \[ a'2 bes' \] }
(As a workaround, is there any way to make the brackets and
accidentals not try to avoid each other at all? This seems to be the
case with brackets
On Sat, Dec 15, 2012 at 06:12:50AM +1100, Nick Payne wrote:
The link to lyqi at
http://lilypond.org/doc/v2.17/Documentation/web/easier-editing is
not valid (the page http://nicolas.sceaux.free.fr/lilypond/lyqi.html
doesn't exist. The correct link now appears to be
On Sat, Dec 15, 2012 at 09:26:57PM +, Keith OHara wrote:
Federico Bruni fedelogy at gmail.com writes:
I'm a bit confused about the use of minimumFret and restrainOpenString.
Maybe adding a warning in the documentation could be a good idea.
It seems that restrainOpenString = #t causes
Il 16/12/2012 10:12, Colin Hall ha scritto:
Federico, I reproduced your output, which looks fine to me, but I am
not a fret player.
So, perhaps you could explain exactly what is wrong and I can add your
comment to the tracker? There's a png of the output on the tracker.
New tracker here:
On Sun, Dec 16, 2012 at 12:31:45AM -0800, Eluze wrote:
Ben Rudiak-Gould wrote
% The end of the ligature bracket is not printed
\version 2.17.8
{ \[ c'1 \break d'1 \] }
see NR
http://www.lilypond.org/doc/v2.17/Documentation/notation/ancient-notation_002d_002dcommon-features#ligatures
On Sun, Dec 16, 2012 at 12:42:16AM -0800, Eluze wrote:
Ben Rudiak-Gould wrote
% The flat symbol is unreasonably far above the note
\version 2.17.8
{ \set suggestAccidentals = ##t \[ a'2 bes' \] }
(As a workaround, is there any way to make the brackets and
accidentals not try to
On Sun, Dec 16, 2012 at 08:07:53AM +0100, Mike Solomon wrote:
Hey all,
A colleague of mine got the following error message while running midi2ly on
his MacBook :
macbook:~ vanhovef$ /Applications/LilyPond.app/Contents/Resources/bin/midi2ly
wil
Traceback (most recent call last):
File
On 16 déc. 2012, at 10:54, Colin Hall colingh...@gmail.com wrote:
On Sun, Dec 16, 2012 at 08:07:53AM +0100, Mike Solomon wrote:
Hey all,
A colleague of mine got the following error message while running midi2ly on
his MacBook :
macbook:~ vanhovef$
On Sun, Dec 16, 2012 at 10:29:55AM +0100, Federico Bruni wrote:
Il 16/12/2012 10:12, Colin Hall ha scritto:
Federico, I reproduced your output, which looks fine to me, but I am
not a fret player.
So, perhaps you could explain exactly what is wrong and I can add your
comment to the tracker?
On Sun, Dec 16, 2012 at 10:56:57AM +0100, Mike Solomon wrote:
On 16 déc. 2012, at 10:54, Colin Hall colingh...@gmail.com wrote:
On Sun, Dec 16, 2012 at 08:07:53AM +0100, Mike Solomon wrote:
Hey all,
A colleague of mine got the following error message while running midi2ly
on his
Il 16/12/2012 11:06, Colin Hall ha scritto:
It wasn't clear to me from Keith's post that the re-opened issue
was responsible for what you were seeing.
If you could jointly confirm that issue 2348 will resolve your thing
then yes, we can close off the new tracker.
I confirm it
On Sun, Dec 16, 2012 at 02:50:25PM +0700, Yevgeny Lezhnin wrote:
issue 2990 : lilypond crashes with a stack overflow on Windows (1)
also tested in Linux, also crash
There is infinite loop in calc_skylines function, I don't know yet,
what may cause it.
This is quotes from discussion with
Colin Hall-3 wrote
Eluze, do we have an open issue on the tracker for this incomplete
feature? Searching the tracker all I could find was:
http://code.google.com/p/lilypond/issues/list?can=2q=ligaturecolspec=ID+Type+Status+Stars+Owner+Patch+Needs+Summaryx=typecells=tiles
all I could find
On Sun, Dec 16, 2012 at 02:34:21AM -0800, Eluze wrote:
Colin Hall-3 wrote
Eluze, do we have an open issue on the tracker for this incomplete
feature? Searching the tracker all I could find was:
Il 08/12/2012 19:44, Ralph Palmer ha scritto:
On Sat, Dec 8, 2012 at 5:14 AM, Federico Bruni fedel...@gmail.com
mailto:fedel...@gmail.com wrote:
Shouldn't the slur go from the note inside of the chord which it
actually starts on to the note which it
actually ends on?
This
The predefined command \textLengthOn no longer always permits
TextScripts to align. I suspect it broke when the new skylining code
was implemented, but I haven't verified this.
\textLengthOn is defined to be
\override TextScript.extra-spacing-width = #'(0 . 0)
\override
Trevor Daniels t.dani...@treda.co.uk wrote in message
news:assp.0697eb5db6.EB380C5E80F04264B181F9417B1D3AAD@TrevorLaptop...
The predefined command \textLengthOn no longer always permits
TextScripts to align. I suspect it broke when the new skylining code
was implemented, but I haven't verified
On Sun, Dec 16, 2012 at 6:23 AM, Federico Bruni fedel...@gmail.com wrote:
Here the examples:
\version 2.17.9
music = \relative c' {
% Example 1: only TabStaff is wrong and can be corrected with an override
%\once \override TabVoice.Slur.direction = #DOWN
g\4 b\2\4\glissando (
On 16 déc. 2012, at 14:38, Phil Holmes m...@philholmes.net wrote:
Trevor Daniels t.dani...@treda.co.uk wrote in message
news:assp.0697eb5db6.EB380C5E80F04264B181F9417B1D3AAD@TrevorLaptop...
The predefined command \textLengthOn no longer always permits
TextScripts to align. I suspect it
In the following example :
\version 2.17.9
\relative c' { g a' a r4 a1 }
\addlyrics { u u u u }
\relative c''' { r2 r32 d8.. r4 R1 }
I'm not convinced that the lower voice should slice through the lyrics. I'm
typesetting a choral works and it looks, while sightreading, that the u in the
On Sun, Dec 16, 2012 at 12:42:16AM -0800, Eluze wrote:
here's a first tweak to improve the output:
\override LigatureBracket.outside-staff-priority = #200
\override AccidentalSuggestion.outside-staff-priority = #100
This is definitely an improvement, thanks. I also tried various values
of
m...@mikesolomon.org wrote in message
news:4f340ef1-b01d-4332-bc06-88b0cb1ff...@mikesolomon.org...
In the following example :
\version 2.17.9
\relative c' { g a' a r4 a1 }
\addlyrics { u u u u }
\relative c''' { r2 r32 d8.. r4 R1 }
I'm not convinced that the lower voice should slice
On 16 déc. 2012, at 18:37, Phil Holmes m...@philholmes.net wrote:
m...@mikesolomon.org wrote in message
news:4f340ef1-b01d-4332-bc06-88b0cb1ff...@mikesolomon.org...
In the following example :
\version 2.17.9
\relative c' { g a' a r4 a1 }
\addlyrics { u u u u }
\relative c''' { r2
On Sun, Dec 16, 2012 at 12:31 AM, Eluze elu...@gmail.com wrote:
http://www.lilypond.org/doc/v2.17/Documentation/notation/ancient-notation_002d_002dcommon-features#ligatures
Known issues and warnings
Ligatures need special spacing that has not yet been implemented. As a
result, there is too
m...@mikesolomon.org wrote in message
news:4e267bda-b3ac-419b-83c4-4f10c3980...@mikesolomon.org...
On 16 déc. 2012, at 18:37, Phil Holmes m...@philholmes.net wrote:
m...@mikesolomon.org wrote in message
news:4f340ef1-b01d-4332-bc06-88b0cb1ff...@mikesolomon.org...
In the following example :
On 16 déc. 2012, at 18:46, Phil Holmes m...@philholmes.net wrote:
m...@mikesolomon.org wrote in message
news:4e267bda-b3ac-419b-83c4-4f10c3980...@mikesolomon.org...
On 16 déc. 2012, at 18:37, Phil Holmes m...@philholmes.net wrote:
m...@mikesolomon.org wrote in message
m...@mikesolomon.org wrote Sunday, December 16, 2012 4:43 PM
Trevor Daniels t.dani...@treda.co.uk wrote in message
news:assp.0697eb5db6.EB380C5E80F04264B181F9417B1D3AAD@TrevorLaptop...
The predefined command \textLengthOn no longer always permits
TextScripts to align. I suspect it broke
I have hacked something up (see code below), but it doesn't work very well:
* It works for slurs on either end as long as they span at least two
notes. I can get it to work with single-note slurs at the end of the
line by writing c'( s1*0) or c'( ), but I get the warning
programming error: bounds
Here is a suggestion for clarifying the documentation of advanced command-line
options, from a command-line beginner.
http://www.lilypond.org/doc/v2.16/Documentation/usage/command_002dline-usage#advanced-command-line-options-for-lilypond
I wanted to try SVG output, and after reading that page I
On Sun, Dec 16, 2012 at 12:23:29PM +0100, Federico Bruni wrote:
Il 08/12/2012 19:44, Ralph Palmer ha scritto:
On Sat, Dec 8, 2012 at 5:14 AM, Federico Bruni fedel...@gmail.com
mailto:fedel...@gmail.com wrote:
Shouldn't the slur go from the note inside of the chord which it
actually
Hello,
On 16 December 2012 18:12, Paul Morris p...@paulwmorris.com wrote:
Here is a suggestion for clarifying the documentation of advanced
command-line options, from a command-line beginner.
On 15 December 2012 16:58, David Nalesnik david.nales...@gmail.com wrote:
The Measure_counter_engraver is part of LilyPond as of 2.17.7. There
isn't any documentation yet. (For one thing, I'm unsure of where to
put it as it requires adding the engraver to a context. Would a
snippet be the
Hi,
Now that Measure_counter_engraver has been implemented into LilyPond
people can add a measure counter (great, thanks).
But unfortunately people have to start it and stop it _manually_,
using \startMeasureCount and \stopMeasureCount.
Could we add a feature to have an _automatic_ measure
Hi,
I see that David Kastrup is currently fixing issue #1029
\thumb should behave like other fingerings, thank you.
Does that mean that after the fix has been pushed \thumb will be
engraved by Fingering_engraver (or New_Fingering_engraver, I do
not understand why there are two engravers)?
So
I can not compile files with lilypond-book in the recomended, stable Version
2.16.1. Older and Newer Versions (2.16.0 / 2.17.8) work without problems.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Chris,
On 16 December 2012 20:41, Chris lubese...@gmx.de wrote:
I can not compile files with lilypond-book in the recomended, stable Version
2.16.1. Older and Newer Versions (2.16.0 / 2.17.8) work without problems.
Can you give an example?
Maybe attach a file although if you can get a tiny
On lilypond-devel, Xavier Scheuer writes:
Would it be possible to add a command for finger changes, so that
they are engraved by Fingering_engraver (New_Fingering_engraver)
also?
Currently the doc says
Markup texts may be used for finger changes.
c4-1 d-2 f-4 c^\markup { \finger 2 - 3 }
but
40 matches
Mail list logo