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
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.
Chee
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
Nick Payne 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
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
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, an
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
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.
___
bu
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 ass
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
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 p
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
conti
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-len
On 12/6/11 3:26 PM, "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.alterna
> 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.ht
2011/12/7 Francisco Vila :
> 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-li
2011/12/7 Francisco Vila :
> 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
2011/12/7 Xavier Scheuer :
> 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 ach
On 7 December 2011 02:58, huzzam 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
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,
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 l
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 cr
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
> 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-pag
> 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 th
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 ha
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
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^
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
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
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 {
{
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-lilypon
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
33 matches
Mail list logo
