[EMAIL PROTECTED] writes:
> Starting in line 1270 of refman.itely:
>
> The following commands specify in what chords of the current voice
> should be shifted: the outer voice has @code{\shiftOff}, and the inner
> voices have @code{\shiftOn}, @code{\shiftOnn}, etc.
>
> @cindex @code{\shiftOn}
> @c
[EMAIL PROTECTED] writes:
> I'm working on proof-reading the manual. From refman.itely starting on
> line 1721:
>
> This example shows two examples of the same music giving different
> accidentals depending on the order in which the notes occur in the
> input file:
>
> @lilypond[raggedright,fragm
http://lilypond.org/doc/v2.1/input/regression/out-www/lily-1485554506.ly
Same as subject... only a bug report
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
% In the second note from the right ( a-. ) the staccato dot collides with
% rows extension (dash)
\version "2.1.26"
\paper {
linewidth = 200\pt
}
\score {
\context Staff = violino { #(set-accidental-style 'modern)
\notes \relative c''' {
\overr
I'm working on proof-reading the manual. From refman.itely starting on
line 1721:
This example shows two examples of the same music giving different
accidentals depending on the order in which the notes occur in the
input file:
@lilypond[raggedright,fragment,verbatim]
\set Staff.autoAccidentals =
Starting in line 1270 of refman.itely:
The following commands specify in what chords of the current voice
should be shifted: the outer voice has @code{\shiftOff}, and the inner
voices have @code{\shiftOn}, @code{\shiftOnn}, etc.
@cindex @code{\shiftOn}
@code{\shiftOn},
@cindex @code{\shiftOnn}
@
What i used to do is to use the figured bass engraver, but with text,
so i must change the default font which only brings numbers by
another one with text:
% i.e.
%
analysis = \figures {
\property FiguredBass.BassFigure \override #'font-name = #"cmr17"
\property FiguredBass.BassF
> Yes, but it also takes me extra time. (I'm a lazy bum). You can
> subscribe to [EMAIL PROTECTED] to get the latest scoops.
Thanks for the tip. You should mention this list on
http://lilypond.org/web/documentation.html
where you should also change "Bugreports" to "Bug reports".
--
http://www.
On Wed, 25 Feb 2004, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > As well as the cumulative 2.0->2.1 release notes, it would be very helpful
> > to have per-release release notes, so one can see what has changed between
> > individual releases.
>
> Yes, but it also takes me extra tim
[EMAIL PROTECTED] writes:
>
> I had a cold sweat when running the new 2.1.26, but then read:
> "The naming of exported Scheme functions now follows Scheme conventions."
> Ouf.
>
> This is just a suggestion:
> It may be more idiomatic to define a setter for accessors. For
> instance, given the rea
[EMAIL PROTECTED] writes:
> As well as the cumulative 2.0->2.1 release notes, it would be very helpful
> to have per-release release notes, so one can see what has changed between
> individual releases.
Yes, but it also takes me extra time. (I'm a lazy bum). You can
subscribe to [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
>[the NEWS file]
> Are new changes always added to the top?
Yes.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mail
On Tue, 24 Feb 2004, Edward Sanford Sutton, III wrote:
> I know a chord can be labeled as Cm, but is there a way to label them for
> harmonic analysis? I have only figured out how to get so far with stuff like:
>
> _\markup "i"
>
> The last time I attempted such markings was on a cadential
All these alternatives should give the same result.
Yet another alternative which saves another key stroke is
dvips -Ppdf -u+lilypond lilybook
/Mats
David Bobroff wrote:
From tutorial.itely (lines 1830-1835):
To convert the file into a nice PDF document, run the following
commands:
@example
$
14 matches
Mail list logo