Re: Issue 2037 in lilypond: Patch: Bring argument processing of chord music functions in line with the rest
Updates: Status: Duplicate Labels: -Patch-needs_work Mergedinto: 2070 Comment #5 on issue 2037 by d...@gnu.org: Patch: Bring argument processing of chord music functions in line with the rest http://code.google.com/p/lilypond/issues/detail?id=2037 The problem analyzed in comment 3 is pretty fundamental to this approach. I don't see a reasonable way around it. Doing this right would appear to require the approach in issue 2070. The advantage of that approach would be that it is straightforward to understand and requires no special rules whatsoever for music functions as chord constituents. The disadvantage is that it has a larger impact. I don't have a Status properly reflecting abandoning an issue for another different one (after all, the issue is not invalid), so I am marking this (not quite correctly) as a duplicate of 2070. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default.
Comment #5 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord around rhythmic events by default. http://code.google.com/p/lilypond/issues/detail?id=2070 Issue 2037 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2083 in lilypond: \break in alternative causes score to split
Comment #1 on issue 2083 by mts...@gmail.com: \break in alternative causes
score to split
http://code.google.com/p/lilypond/issues/detail?id=2083
Sorry, I think the example above compiles fine. Better example:
music =
\relative c' {
\repeat volta 2 {
c1 |
}
\alternative {
{
c \bar \break
c |
}
{
c c |
}
}
}
{
\music
\music
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2083 in lilypond: \break in alternative causes score to split
Updates:
Labels: -Type-Critical Type-Ugly
Comment #2 on issue 2083 by mts...@gmail.com: \break in alternative causes
score to split
http://code.google.com/p/lilypond/issues/detail?id=2083
OK, really sorry for the noise...here is an example that has one bit you
can comment out to see the problem. This definitively works. However, as
it is also broken in 2.14.0, I'm downgrading this from critical to plain
old ugly.
Cheers,
MS
music =
#(define-music-function (parser location)
()
#{
\relative c' {
\repeat volta 3 {
c1 |
c |
c |
}
\alternative {
{
c c \break | %% COMMENT OUT BREAK TO SEE CHANGE
}
{
c c |
}
{
c c |
}
}
c c
}
#})
{
\music
\music
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with )
Updates: Labels: Patch-new Comment #8 on issue 2076 by pkx1...@gmail.com: Doc: improve NR 1.6.3 Instrument names (better to use \with ) http://code.google.com/p/lilypond/issues/detail?id=2076 Thanks to you both Xavier and David. Patch uploaded http://codereview.appspot.com/5448129 James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
script-accidental avoidance fails for articulations
See the output of this augmented version of
script-accidental-collision.ly: in the second half the collision
avoidance does not work.
\version 2.15.15
\header {
texidoc = Scripts use skylines with accurate boxes to avoid accidentals.
}
{
ees''1^\espressivo
e''!1^\espressivo
eis''1^\espressivo
ees''1^\fermata
e''!1^\fermata
eis''1^\fermata
ees'1_\espressivo
e'!1_\espressivo
eis'1_\espressivo
ees'1_\fermata
e'!1_\fermata
eis'1_\fermata
ees''^\espressivo1
e''!^\espressivo1
eis''^\espressivo1
ees''^\fermata1
e''!^\fermata1
eis''^\fermata1
ees'_\espressivo1
e'!_\espressivo1
eis'_\espressivo1
ees'_\fermata1
e'!_\fermata1
eis'_\fermata1
}
inline: script-accidental-collision.png
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Overriding stencil of StringNumber leads to programming error messages
Hi,
the awful spacing of input/regression/tablature-harmonic-functions.ly
let me to investigate, and it is apparently due to StringNumber being
set to transparent, meaning that it still occupies space. I tried now
to do
\new Voice \with { \override StringNumber #'stencil = ##f }
{ \clef treble_8
e,1 | % check whether tab note head is restored
\harmonicByFret #12 e'4\1 ~
\harmonicByFret #12 e'4\1 (
\ottava #1
\harmonicByFret #7 e'4\1)
\harmonicByFret #5 e'8\1
\ottava #2
\harmonicByFret #4 b\2 e'\1 8 |
\harmonicByFret #3 g\3 b\2 e'\1 4
\harmonicByFret #2.7 g\3 b\2 e'\1 4
\harmonicByFret #2.3 g\3 b\2 e'\1 4
\harmonicByFret #2 g\3 b\2 e'\1 4 |
\ottava #0
}
instead (removing the New_fingering_engraver is not an option since it
is responsible for more than just string numbers), but I get programming
errors in return:
Interpreting music...
Preprocessing graphical objects...
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `test.ps'...
Converting to `./test.pdf'...
Success: compilation successfully completed
Compilation finished at Wed Dec 7 11:57:07
I think this should be made to work.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing
Comment #8 on issue 2069 by mts...@gmail.com: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing http://code.google.com/p/lilypond/issues/detail?id=2069 Hey all, I'm gonna hold off on pushing this until I push the hairpin patch, which has some changes to has-span-bar that'll make this patch push cleaner. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: DOC NR 1.6.3 - quoting other voices (german doc) and formatiing cue notes (english)
Can you provide your request in English, please? Thanks!
Because my comment concerns only the german version of NR, I think its not
useful to provide it in english. (Perhaps there is another place than
gmane.comp.gnu.lilypond.bugs
to post that, but I don't know, where.)
But by the way:
In the given examples i miss some very easy example without defining \addQuote
and quoting!
I often need cue notes just to print alternetive notes for players, who cannot
play a very high or very low tone. Or I need cue note to give an ad.lib. figure.
Not for quoting other voices!
(At least in german the word „Stichnote“ stands for such quoting cue notes AND
for alternative notes as i mentioned.)
In the following lilypond file I give some snippets - maybe some of that could
be added to the doc. (I wrote about that already 2009-07-27 11:05:29 GMT on
gmane.comp.gnu.lilypond.devel/22828)
There are two questions about possible buggy behavior in it too.
\version 2.13.47
\header {
title = cue notes / Stichnoten
tagline = ##f
}
\paper {
#(set-paper-size a4)
top-margin = 0.85\cm
bottom-margin = 0.85\cm
left-margin = 1.1\cm
right-margin = 1.1\cm
ragged-last-bottom = ##t
}
#(set-global-staff-size 21)
\include deutsch.ly
% One can obtain cue notes starting a cue voice:
% (using polyphony with {} \\ {} see NR 1.5.2 “The double
% backslash construct”)
{
\clef G
\relative c''
{ \times 2/3 {g4 g g } \times 2/3 {a4 a a} |
\times 2/3 {b4 b b} \times 2/3 {cis4 d e} |
a,1 | \new CueVoice { r8 a \noBeam h-^ a c-^ a \noBeam cis-^ a |
d2 c~ | c2 es4 d | } \\ { r1 | d1~ | d2 c4 b | }
a2 g2~ | g2. r4 | }
}
% (Warning: the CueVoice behaves like OneVoice also in the \\ polyphony
% context. Therefore add stemDirection.)
% Accent to far away from notehead!!!
% IS THAT SUBJECT TO A BUG REPORT???
{
\clef G
\relative c''
{ \times 2/3 {g4 g g } \times 2/3 {a4 a a} |
\times 2/3 {b4 b b} \times 2/3 {cis4 d e} |
a,1 | \new CueVoice { \stemUp { r8 a \noBeam h- a c-^ a \noBeam cis-^ a |
d2 c~ | c2 es4 d | }} \\ { d,1 \rest | d'1~ | d2 c4 b | }
a2 g2~ | g2. r4 | }
}
% (Alternatives can also be given as ossia, see “ossia”.)
% Often cue-notes are given as alternative to other notes or to rests.
% (Also cue notes often are added to rests in one voice quoting other
% voices, to find the start after the rests, about quoting see section
% “quoting other voices”).
% Examples for alternative lower notes:
{
\clef G
\relative c'
{ h'2 a4 g | c2 d4 e | { f2 g4 f } \\ \new CueVoice { e4 d e f } |
e2 r | }
}
% strange long stems (to my taste):
{
\clef G
\relative c''
{ h'2 a4 g | c2 d4 e | { f2 g4 f } \\ \new CueVoice { e4 d e f } |
e2 r | }
}
{
\clef F
\relative c,
{ es4 es' {es'4 d8 d~ | d4 f cis8 a f es | d4 c' c h8 b~ | b1 | } \\
\new CueVoice { \stemDown es,4 d8 d~ | d4 f cis8 a f es | d4 c' c h8 b~ |
b1 | \stemNeutral } r4 r8 b' a4. g8 | f4 es8 d~ d2 | }
}
% Example for alternative higher notes:
{
\clef F
\relative c
{ es4 es \new CueVoice { \stemUp es } \\ es, es' | c g' c,2
c g' c,2 }
}
% or
{
\clef F
\relative c
{ \new CueVoice { s4 s \stemUp es s} \\ { es es es, es' } |
c g' c,2 }
}
% strange accidentals:
% I think one b in one voice in one bar would
% be enough, if needed, one gets another one with es! or es?
% IS THAT SUBJECT TO A BUG REPORT???
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: DOC NR 1.6.3 - quoting other voices (german doc) and formatiing cue notes (english)
In the given examples i miss some very easy example without defining \addQuote and quoting! Sorry - i just found out, that i wrote about http://lilypond.org/doc/v2.12/Documentation/user/lilypond-big-page#Writing-parts instead of http://lilypond.org/doc/v2.14/Documentation/notation-big-page#writing-parts So only the questions about accents and accidentals remain. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2083 in lilypond: \\break in alternative causes score to split
this is described in
http://lilypond.org/doc/v2.15/Documentation/usage/common-errors#Common-errors
it points to the fact that there are … two \relative blocks, which each
implicitly create Staff and Voice blocks.
the following example creates a separate staff, too:
{
\relative c' c
\relative c' d
}
if in your example you only use \music once everything looks OK!
Eluze
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2083 in lilypond: \\break in alternative causes score to split
Le Dec 7, 2011 à 1:07 PM, Eluze a écrit :
this is described in
http://lilypond.org/doc/v2.15/Documentation/usage/common-errors#Common-errors
it points to the fact that there are … two \relative blocks, which each
implicitly create Staff and Voice blocks.
the following example creates a separate staff, too:
{
\relative c' c
\relative c' d
}
if in your example you only use \music once everything looks OK!
Eluze
Gotchya...sorry for missing that!
Will mark as invalid.
Cheers,
MS
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2083 in lilypond: \break in alternative causes score to split
Updates: Status: Invalid Comment #3 on issue 2083 by mts...@gmail.com: \break in alternative causes score to split http://code.google.com/p/lilypond/issues/detail?id=2083 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Set global staff size as command line option
Hi, Is it possible to set global staff size as command line option? Like it is possible to specify paper size with lilypond -dpaper-size=\letter\ myfile.ly I'd like a similar command line option for #(set-global-staff-size 14) . Is there a way to achieve this with current version? Anyway, I think that would be a nice new feature. Dear bug squad, could you add this request on the tracker ? Thanks! Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Where to put user ly files on OSX?
On 7 December 2011 02:58, huzzam clari...@huzzam.com wrote: Hi-- I'm fairly new to lilypond, and am starting to write my own ly files to include. I want to put them somewhere that will be accessible easily from any score (user defaults). The only place I've so far been able to find to put them is inside the lilypond application package itself (/Applications/Lilypond.app/Contents/Resources/share/lilypond/current/ly). This obviously is annoying when I upgrade lilypond, as I have to dig in there and copy my files to the new one. Is there some place I can put them so that I can still just \include asdf.ly (without a path), but which is not inside the package itself? Something along the lines of ~/Library/lilypond or /usr/share/lilypond? There is not such features in LilyPond yet (but I'd love this too). Denis made a similar request on lilypond-devel a few days ago. http://lists.gnu.org/archive/html/lilypond-devel/2011-12/msg00073.html No developer replied at the moment; I hope one will say something about it. Then I suppose it could be added to the tracker (cc: to bug-lilypond) as a new feature request. Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Set global staff size as command line option
2011/12/7 Francisco Vila paconet@gmail.com: It is a way but the problem I find is that the file won't compile with that commandline option. Oh sorry, I meant the file won't compile _without_ that commandline option. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Set global staff size as command line option
2011/12/7 Francisco Vila paconet@gmail.com: lilypond -e '(define-public size 40)' a.ly And of course there were more typos. It is not a.ly but example.ly in my example above. Sorry! -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: DOC NR 1.6.3 - quoting other voices (german doc)
So only the questions about accents and accidentals remain. And the german-translation-problem of course, btw - the german version http://lilypond.org/doc/v2.14/Documentation/notation-big-page.de.html#quoting- other-voices and http://lilypond.org/doc/v2.14/Documentation/notation-big-page.de.html#formatting- cue-notes is still in the state of v2.12. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2059 in lilypond: Bar numbering of alternatives
On 12/6/11 3:26 PM, lilyp...@googlecode.com lilyp...@googlecode.com wrote: Comment #14 on issue 2059 by x.sche...@gmail.com: Bar numbering of alternatives http://code.google.com/p/lilypond/issues/detail?id=2059 The use of this \set Score.alternativeNumberingStyle = #'number or \set Score.alternativeNumberingStyle = #'numbers-with-letters deserves an explanation (as a snippet) in the notation reference, NR 1.4.1 Long repeats and maybe a cross-reference in NR 1.2.5 Bars Bar numbers and this new feature deserves an entry in 'Documentation/changes.tely' IMHO Thank you! Xavier This should become a new issue, type Documentation. Thanks, Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
bug or feature with the extent of NoteColumn with 2.15.20 ?
Hi,
trying to compile a function manipulating the NoteColumn with 2.15.20 I
noticed some differences to 2.14.2
So I wrote a test-function to display the grob-length:
\version 2.14.2
%\version 2.15.20
#(define (x-length-of-grob grob)
(let* ((sys (ly:grob-system grob))
(grob-length (interval-length (ly:grob-extent grob sys X
(newline)
(display grob-length)))
\relative c' {
\override NoteColumn #'after-line-breaking = #x-length-of-grob
c e4
c e4.
c eis4
c eis4\arpeggio
}
With 2.14.2 I get:
1.316178
1.316178
1.316178
1.316178
With 2.15.20 I get:
1.316178
1.316178
1.316178
2.616182
It seems that in 2.15.20 the arpeggio is part of the NoteColumn. (But not
the DotColumn or the AccidentalPlacement)
The IR 3.2.71 note-column-interface states only stems and noteheads.
-
http://lilypond.org/doc/v2.15/Documentation/internals-big-page#note_002dcolumn_002dinterface
Is this a bug or a feature for something?
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2057 in lilypond: Hairpin hits barline at line break
Comment #37 on issue 2057 by k-ohara5...@oco.net: Hairpin hits barline at line break http://code.google.com/p/lilypond/issues/detail?id=2057 Now that the original code is working as intended, I see that it makes a distinction between hairpins that end at the end of a line those that continue on the next line. I'd like to keep that distinction. Attachments: 2057.png 31.2 KB 2057.ly 383 bytes ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Unable to find file lily.scm in load path
I was using Lilypond with no problems yesterday (2.15.20 on Ubuntu 10.04 amd64). I noticed 2.15.21 on lilypond.org this morning, so I downloaded the Linux 64 version, ran uninstall-lilypond, and installed 2.15.21. On any attempt to run Lilypond I got: GNU LilyPond 2.15.21 ERROR: In procedure primitive-load-path: ERROR: Unable to find file lily.scm in load path I rebooted, ran uninstall-lilypond again and reinstalled 2.15.20 from the download I still had from my initial install of 2.15.20, but got exactly the same error message from 2.15.20, so I ran lilypond inside strace. This seems to be the relevant portion of the strace log file - the last couple of dozen lines: stat(/home/nick/lilypond/scm/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/home/nick/lilypond/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/usr/local/lilypond/usr/bin/../share/guile/1.8/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/usr/share/guile/site/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/usr/share/guile/1.8/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/usr/share/guile/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) write(2, ERROR, 5)= 5 write(2, : , 2) = 2 write(2, In procedure , 13) = 13 write(2, primitive-load-path, 19) = 19 write(2, :\n, 2) = 2 write(2, ERROR, 5)= 5 write(2, : , 2) = 2 write(2, Unable to find file , 20)= 20 write(2, \, 1) = 1 write(2, lily.scm, 8) = 8 write(2, \, 1) = 1 write(2, in load path, 13) = 13 write(2, \n, 1) = 1 close(4)= 0 close(5)= 0 exit_group(1) = ? lily.scm is in /usr/local/lilypond/usr/share/lilypond/current/scm, which is where I would expect it to be. Any suggestions on how to fix this problem? Nick ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2057 in lilypond: Hairpin hits barline at line break
Comment #38 on issue 2057 by prze...@gmail.com: Hairpin hits barline at line break http://code.google.com/p/lilypond/issues/detail?id=2057 It looks it went in good direction except for hairpins touching span bar in case of those continuing on the next line: - they should still have padding at the end of line (but much smaller one than normally, like 1/6), - their height should be only some fraction of full height (I would suggest 2/3 [instead of 1 as it is now] at the end of line and 1/3 at the next line for crescendo and reversed values for decrescendo). Fixing it will improve readability and overall look. Also for testing I would suggest using different staves, to check whether hairpin horizontal placement and length is the same for corresponding notes of different individual intervals, but equal summary one. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 460 in lilypond: bar numbers for broken bars
Updates: Labels: Patch-review Comment #9 on issue 460 by lilypond...@gmail.com: bar numbers for broken bars http://code.google.com/p/lilypond/issues/detail?id=460#c9 Patchy the autobot says: LGTM. in tuplet-broken.ly, I see a bar number on the third system but not the second. I assume that's correct? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with )
Updates: Labels: Patch-review Comment #9 on issue 2076 by lilypond...@gmail.com: Doc: improve NR 1.6.3 Instrument names (better to use \with ) http://code.google.com/p/lilypond/issues/detail?id=2076#c9 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2084 in lilypond: script-accidental avoidance fails for articulations
Status: Accepted
Owner:
CC: d...@gnu.org
New issue 2084 by idragos...@gmail.com: script-accidental avoidance fails
for articulations
http://code.google.com/p/lilypond/issues/detail?id=2084
See the output of this augmented version of
script-accidental-collision.ly: in the second half the collision
avoidance does not work.
\version 2.15.15
\header {
texidoc = Scripts use skylines with accurate boxes to avoid accidentals.
}
{
ees''1^\espressivo
e''!1^\espressivo
eis''1^\espressivo
ees''1^\fermata
e''!1^\fermata
eis''1^\fermata
ees'1_\espressivo
e'!1_\espressivo
eis'1_\espressivo
ees'1_\fermata
e'!1_\fermata
eis'1_\fermata
ees''^\espressivo1
e''!^\espressivo1
eis''^\espressivo1
ees''^\fermata1
e''!^\fermata1
eis''^\fermata1
ees'_\espressivo1
e'!_\espressivo1
eis'_\espressivo1
ees'_\fermata1
e'!_\fermata1
eis'_\fermata1
}
Attachments:
script-accidental-collision.png 3.7 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages
Status: Accepted
Owner:
New issue 2085 by idragos...@gmail.com: Overriding stencil of StringNumber
leads to programming error messages
http://code.google.com/p/lilypond/issues/detail?id=2085
the awful spacing of input/regression/tablature-harmonic-functions.ly
let me to investigate, and it is apparently due to StringNumber being
set to transparent, meaning that it still occupies space. I tried now
to do
\new Voice \with { \override StringNumber #'stencil = ##f }
{ \clef treble_8
e,1 | % check whether tab note head is restored
\harmonicByFret #12 e'4\1 ~
\harmonicByFret #12 e'4\1 (
\ottava #1
\harmonicByFret #7 e'4\1)
\harmonicByFret #5 e'8\1
\ottava #2
\harmonicByFret #4 b\2 e'\1 8 |
\harmonicByFret #3 g\3 b\2 e'\1 4
\harmonicByFret #2.7 g\3 b\2 e'\1 4
\harmonicByFret #2.3 g\3 b\2 e'\1 4
\harmonicByFret #2 g\3 b\2 e'\1 4 |
\ottava #0
}
instead (removing the New_fingering_engraver is not an option since it
is responsible for more than just string numbers), but I get programming
errors in return:
Interpreting music...
Preprocessing graphical objects...
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
programming error: cannot align on self: empty element
continuing, cross fingers
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `test.ps'...
Converting to `./test.pdf'...
Success: compilation successfully completed
Compilation finished at Wed Dec 7 11:57:07
I think this should be made to work.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unable to find file lily.scm in load path
On 08/12/11 12:06, Nick Payne wrote: I was using Lilypond with no problems yesterday (2.15.20 on Ubuntu 10.04 amd64). I noticed 2.15.21 on lilypond.org this morning, so I downloaded the Linux 64 version, ran uninstall-lilypond, and installed 2.15.21. On any attempt to run Lilypond I got: GNU LilyPond 2.15.21 ERROR: In procedure primitive-load-path: ERROR: Unable to find file lily.scm in load path I rebooted, ran uninstall-lilypond again and reinstalled 2.15.20 from the download I still had from my initial install of 2.15.20, but got exactly the same error message from 2.15.20, so I ran lilypond inside strace. This seems to be the relevant portion of the strace log file - the last couple of dozen lines: stat(/home/nick/lilypond/scm/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/home/nick/lilypond/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/usr/local/lilypond/usr/bin/../share/guile/1.8/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/usr/share/guile/site/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/usr/share/guile/1.8/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/usr/share/guile/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) write(2, ERROR, 5)= 5 write(2, : , 2) = 2 write(2, In procedure , 13) = 13 write(2, primitive-load-path, 19) = 19 write(2, :\n, 2) = 2 write(2, ERROR, 5)= 5 write(2, : , 2) = 2 write(2, Unable to find file , 20)= 20 write(2, \, 1) = 1 write(2, lily.scm, 8) = 8 write(2, \, 1) = 1 write(2, in load path, 13) = 13 write(2, \n, 1) = 1 close(4)= 0 close(5)= 0 exit_group(1) = ? lily.scm is in /usr/local/lilypond/usr/share/lilypond/current/scm, which is where I would expect it to be. Any suggestions on how to fix this problem? Well, my really ugly hack that gets LP to run was to copy the entire contents of /usr/local/lilypond/usr/share/lilypond/current into ~/lilypond. After that it runs without error. Nick ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unable to find file lily.scm in load path
Nick Payne nick.pa...@internode.on.net writes: I was using Lilypond with no problems yesterday (2.15.20 on Ubuntu 10.04 amd64). I noticed 2.15.21 on lilypond.org this morning, so I downloaded the Linux 64 version, ran uninstall-lilypond, and installed 2.15.21. On any attempt to run Lilypond I got: GNU LilyPond 2.15.21 ERROR: In procedure primitive-load-path: ERROR: Unable to find file lily.scm in load path I rebooted, ran uninstall-lilypond again and reinstalled 2.15.20 from the download I still had from my initial install of 2.15.20, but got exactly the same error message from 2.15.20, so I ran lilypond inside strace. This seems to be the relevant portion of the strace log file - the last couple of dozen lines: stat(/home/nick/lilypond/scm/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/home/nick/lilypond/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) stat(/usr/local/lilypond/usr/bin/../share/guile/1.8/lily.scm, 0x7fffc5d00d00) = -1 ENOENT (No such file or directory) lily.scm is in /usr/local/lilypond/usr/share/lilypond/current/scm, which is where I would expect it to be. Any suggestions on how to fix this problem? Sure you don't have an executable or even a dead symbolic link in /home/nick/lilypond or /home/nick/bin or so? -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2057 in lilypond: Hairpin hits barline at line break
Comment #39 on issue 2057 by mts...@gmail.com: Hairpin hits barline at line break http://code.google.com/p/lilypond/issues/detail?id=2057 My patch implements the former of your requests (a little bit of padding). I'd like to get it smoothly integrated and then propose a second patch for the height modifications. Send me a reminder if I forget next week. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 460 in lilypond: bar numbers for broken bars
Comment #10 on issue 460 by mts...@gmail.com: bar numbers for broken bars http://code.google.com/p/lilypond/issues/detail?id=460 I'm not sure if it's correct. The first measure number is normally never printed in a score, but I'm not sure about the first parenthesized measure number. Cheers, MS ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 460 in lilypond: bar numbers for broken bars
Comment #11 on issue 460 by lemzw...@gmail.com: bar numbers for broken bars http://code.google.com/p/lilypond/issues/detail?id=460 I suggest to interpret the rule as `don't print a bar number at the beginning of the first system of a piece'. Consequently, I favour that we have `(1)' in the second system for a broken first bar. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
