Re: Doc bug in Snippets HTML: "indepently" should be "independently"

Am Mi., 24. Juni 2020 um 22:05 Uhr schrieb Kenneth Wolcott : > > Doc bug in Snippets HTML: "indepently" should be "independently" in > the snippet titled "Changing the number of augmentation dots per note" > in the "Rhythms" section. > >

Doc bug in Snippets HTML: "indepently" should be "independently"

Doc bug in Snippets HTML: "indepently" should be "independently" in the snippet titled "Changing the number of augmentation dots per note" in the "Rhythms" section. Ken Wolcott ___ bug-lilypond mailing list bu

Re: Doc bug: beams

On 9/27/09 12:47 PM, "Nicolas Sceaux" wrote: > Le 27 sept. 09 à 18:25, Carl Sorensen a écrit : >>> \time 4/4 >>> \repeat unfold 8 a8 >>> %% group 8th notes by 2 >>> \overrideBeamSettings #'Score #'(4 . 4) #'end #'(((1 . 8) . (2 2 2 >>> 2))) >> >> This is a feasible beamSettings overri

Re: Doc bug: beams

Le 27 sept. 09 à 18:25, Carl Sorensen a écrit : \time 4/4 \repeat unfold 8 a8 %% group 8th notes by 2 \overrideBeamSettings #'Score #'(4 . 4) #'end #'(((1 . 8) . (2 2 2 2))) This is a feasible beamSettings override, but it's probably not desirable. The new autobeaming code requires

Re: Doc bug: beams

On 9/27/09 3:27 AM, "Nicolas Sceaux" wrote: > Le 27 sept. 09 à 10:40, Nicolas Sceaux a écrit : > >> or is it considered too advanced for this section? > > Oops, actually this is poor advice, as it does not work well with beam > setting reverts. > Maybe that: > > %% at the end of scm/beam-

Re: Doc bug: beams

, despite the beam settings override on the > 2nd bar. Thanks, Nicolas. This is a doc bug that was created when we got the 4 4 autobeaming right. I will fix it soon. > > Maybe the example should be changed to eg.: > >\time 4/4 >\repeat unfold 8 a8 >%% group 8

Re: Doc bug: beams

Le 27 sept. 09 à 10:40, Nicolas Sceaux a écrit : Perhaps it would be nice to show in this section how to override the default beaming settings globally, in a \layout block; stating that instead of repeating in each score a beam setting override like: \overrideBeamSettings #'Score #'(4 . 4

Doc bug: beams

Hi, It seems that the last example in NR 1.2.4 Beams: Setting automatic beam behavior, is broken. (I'm looking at lilypond.org 2.13.4 doc). This example shows three bars of 16th note, grouped by 4, despite the beam settings override on the 2nd bar. Maybe the example should be changed to e

Re: Doc bug: Span_dynamic_performer

Thanks, fixed in git. Cheers, - Graham Daniel Johnson wrote: In section 10.3.1 of the Fine Manual (for both 2.10 and 2.11), we see the following: To remove dynamics from the MIDI output, insert the following lines in the \midi{} section. \midi { ... \context { \Voice \remove "Dyna

Doc bug: Span_dynamic_performer

In section 10.3.1 of the Fine Manual (for both 2.10 and 2.11), we see the following: To remove dynamics from the MIDI output, insert the following lines in the \midi{} section. \midi { ... \context { \Voice \remove "Dynamic_performer" \remove "Span_dynamic_performer" } } Span_d

Re: doc bug(s)?/beam bug?

I've corrected the two typos in the documentation. For your last question, see below. David Bobroff wrote: Not sure if I've spotted a documentation bug (at the very least there is a typo), a program bug, or some of each. Here goes: In section 8.6.2 "Setting automatic beam behavior" it says;

doc bug(s)?/beam bug?

de-auto-beam-setting '(end * * 2 4) 4 8) ...mean that in 2/4 time four eights should be beamed together? Neither one does that for me on CVS 2.7.20. So, is this a bug, a doc bug, a failure on my part to understand, or some combination of the three? -David _

Re: 2.7[.6] doc: bug? grand staff brace missing

On Sunday 21 August 2005 04.51, Hans Forbrich wrote: > As shown in User manual, section "6.3.7 System start delimiters", the > GrandStaff context example description indicates the system should start > with a brace but the brace is missing. > > http://lilypond.org/doc/v2.7/Documentation/user/out-ww

Re: 2.7[.6] doc: bug? grand staff brace missing

On 22-Aug-05, at 6:20 PM, Hans Forbrich wrote: On August 21, 2005 08:16 pm, you wrote: Thanks for the report!  BTW, in the future could you link to the individual page, instead of the huge "all-in-one" doc page? Sorry about that. Please keep traffic on the mailist. Here's a minimal examp

Re: 2.7[.6] doc: bug? grand staff brace missing

On 21-Aug-05, at 7:16 PM, Graham Percival wrote: Developers, with the binary package on osx (2.7.6-1.dmg), I get this: warning: can't find or create new `Grandstaff' [1] Interestingly, I no longer get this. Since the earlier report, I put lilypond.sh in my path and adjusted the APPLICATION pa

Re: 2.7[.6] doc: bug? grand staff brace missing

On 20-Aug-05, at 7:51 PM, Hans Forbrich wrote: As shown in User manual, section "6.3.7 System start delimiters", the GrandStaff context example description indicates the system should start with a brace but the brace is missing. Thanks for the report! BTW, in the future could you link to t

2.7[.6] doc: bug? grand staff brace missing

As shown in User manual, section "6.3.7 System start delimiters", the GrandStaff context example description indicates the system should start with a brace but the brace is missing. http://lilypond.org/doc/v2.7/Documentation/user/out-www/lilypond.html#System-start-delimiters /Hans -- Proud use

Re: doc bug

On 19-Mar-05, at 7:11 PM, John Williams wrote: lilypond-book --filter='convert-ly --from=2.0.0 -' my-book.tely It might also be nice to tell the user that lilypond book will not --filter and --process at the same time. I assumed that --filter would just do that as an extra step before process

doc bug

lilypond-book --filter example is wrong on Instead of lilypond-book --filter='convert-ly --from=2.0.0' my-book.tely It should have a "-" to read from stdin:

doc bug

Tried to make rpm while there was a doc bug: ./out/lilypond-internals.nexi:9730: Cross reference to nonexistent node `Ligature'. Heikki Junes ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond