My first reply, identifying this bug as a regression ...
- Original Message -
From: "Trevor Daniels"
To: "David Stocker" ;
Sent: Sunday, July 08, 2012 12:48 PM
Subject: Re: Repeat Dots and Staff Size in 2.15.41
> Damn! Another regression. (Sorry, David, I&#
My second reply, identifying a possible source of the bug.
Trevor
- Original Message -
From: "Trevor Daniels"
To: "Trevor Daniels" ; "David Stocker"
;
Sent: Sunday, July 08, 2012 12:52 PM
Subject: Re: Repeat Dots and Staff Size in 2.15.41
>
>
Eluze wrote Monday, July 30, 2012 4:01 PM
> to me both \larger and \smaller are obsolete. or is there a subtlety I can't
> see?
\markup ""
\markup \larger ""
shows a clear difference in size here. Why do you think
they are obsolete?
Some time ago we did change "\bigger" to "\larger".
Eluze, you wrote Monday, July 30, 2012 9:19 PM
> Reinhold Kainhofer wrote:
>>
>> On 2012-07-30 19:43, Trevor Daniels wrote:
>>>
>>> Eluze wrote Monday, July 30, 2012 4:01 PM
>>>
>>>> to me both \larger and \smaller are obsolete. or is the
Ian Hulin wrote Friday, August 17, 2012 11:52 PM
> How about calling this property allow-widow-recto-last-page?
> Maybe it's a bit of a mouthful, but it describes what it does on the
> can: the higher you set the value the less likely it is that
> ly:page-turn-breaking will produce a last page th
While considering how to add a footnotes to TextScript I came across
this, which could be intended or a bug. If the positioning number pair
is set to #'(0 . 0) the footnote mark is located in both x and y directions
on the centre of the TextScript object, but if the values are set to any
non-zero
David Kastrup wrote Tuesday, August 28, 2012 5:10 PM
> "Trevor Daniels" writes:
>
>> While considering how to add a footnotes to TextScript I came across
>> this, which could be intended or a bug. If the positioning number pair
>> is set to #'(0 . 0)
I think I'm running into the same kind of problems David experienced in
tackling issue 2547 - too many of the examples I devise to explain how
to use footnotes simply don't work as they should or at least as I expect.
Here's another example:
\book {
\header { tagline = ##f }
\relative c''
Federico Bruni wrote Sunday, September 02, 2012 6:01 PM
> There's an inconsistency, as it's first stated that -1 causes the text
> to be left-aligned, then that values less than -1 moves the text even
> further to the right.
These are not inconsistent. Remember we are moving an extended
object
Some time ago, around Nov 2011, David folded $(set-time-signature ..)
into the \time command, see
a512132fed73a94068b91fb0bab473319e477b6e.
This change also provides an alternative to \set Timing.beatStructure,
one which seems preferable to me. The use of the new \time command
is undocumente
I'm trying to document footnotes and I have just begun to look at footnotes to
lyrics. There are so many issues with using automatic marks that I think I'll
leave this out of the documentation. Try this:
\score {
<<
{ a' b' c'' d'' }
\addlyrics {
One two
\footnote #'(0.0
David Kastrup wrote Thursday, September 06, 2012 11:49 PM
> David Kastrup writes:
>
>> "Trevor Daniels" writes:
>>
>>> e) The alternative \auto-footnote command would probably work better,
>>> but it gives a syntax error in a Lyrics context.
Federico Bruni wrote Saturday, September 08, 2012 7:45 AM
> I'm reviewing my translation and I found a sentence which doesn't sound
> good to me:
>
> LM 4.1.3
>
> "As we shall see shortly, the properties of different types of object
> are modified by different commands, so it is useful to be
Karl Berry wrote Friday, September 07, 2012 11:45 PM
> Regarding
> http://lilypond.org/doc/v2.16/Documentation/learning/command_002dline
>
> 1) The example there says \version "2.14.2".
> 2) The output in Step 2 starts with "GNU LilyPond 2.14.2". Ok, granted
Thanks. These have already been re
Jean-Charles Malahieude wrote Monday, September 10, 2012 6:57 PM
> The last paragraph of the line breaking section (l. 1460 of
> spacing.itely) (which gets a @c TODO check this) puts me into trouble.
> I think it should be deleted (I've already @ignored it in French):
Yes, it should be deleted.
James Harkins wrote Friday, September 28, 2012 8:08 AM
> The beams on the two e's are omitted in this tiny example (version 2.15.36).
>
> \relative c' { r8 \hideNotes f8 \unHideNotes e8. e16 e2 }
>
>
> The beams are *not* omitted in this tiny example.
>
> \relative c' { r4 e8. e16 e2 }
>
>
Colin Hall wrote Sunday, October 07, 2012 12:29 PM
> On Fri, Oct 05, 2012 at 09:09:02PM +0200, Thomas Morley wrote:
>> 2012/10/5 Carlo Stemberger :
>> > Hi,
>> > I can't change the font size in a Dynamics context. For example:
>> > Is this a bug? (I think so)
>>
>> have a look at /ly/engraver-ini
David Kastrup wrote Wednesday, October 10, 2012 10:27 AM
> Rutger Hofman writes:
>
>> I meet the following bug:
>>
>> \version "2.16.0"
>>
>> {
>> % \override Hairpin #'minimum-length = #5
>> \time 3/4
>> \clef F
>> << e2. { s4\< s4\> s4\!_"poco cresc." } >> |
>> d2. |
>> }
>
Trevor Daniels wrote Wednesday, October 10, 2012 10:40 AM
>
> David Kastrup wrote Wednesday, October 10, 2012 10:27 AM
>
>> Rutger Hofman writes:
>>
>>> I meet the following bug:
>>>
>>> \version "2.16.0"
>>>
>&g
While browsing the Learning Manual I noticed the last example in Section 3.4.4
http://www.lilypond.org/doc/v2.16/Documentation/learning/saving-typing-with-variables-and-functions
displays a fault. It is intended to show the use of 'padding to displace
TextScript, but
the script is not displaced.
Keith OHara wrote Tuesday, November 06, 2012 4:05 AM
> Trevor Daniels treda.co.uk> writes:
>
>> While browsing the Learning Manual I
>> noticed the last example in Section 3.4.4
>> displays a fault. It is intended to show the
>> use of 'padding to dis
Federico Bruni wrote Thursday, November 15, 2012 7:31 AM
> What about adding the following @cindex in
> Documentation/notation/input.itely?
>
> @unnumberedsubsubsec Instrument names
>
> @cindex instrument names
> @cindex MIDI, instrument
> @funindex Staff.midiInstrument
>
> The new one is:
>
Trevor Daniels wrote Thursday, November 15, 2012 4:10 PM
> Good suggestion. Done, although the link will take you to
> the start of the numbered section, NR 3.5.1, rather than
> the unnumberedsubsubsec Instrument names, as the latter
> is not a node. Hhm, perhaps it should be, a
Marek Klein wrote Friday, November 16, 2012 7:46 PM
>
>> Trevor Daniels wrote Thursday, November 15, 2012 4:10 PM
>>
>> > Bugsquad: could you raise an issue to check the docs for
>> > unnumberedsubsubsecs without nodes using the above as
>> > an exam
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 TextScript.extra-spac
m...@mikesolomon.org wrote Sunday, December 16, 2012 4:43 PM
> "Trevor Daniels" wrote in message
> news:assp.0697eb5db6.EB380C5E80F04264B181F9417B1D3AAD@TrevorLaptop...
>> The predefined command \textLengthOn no longer always permits
>> TextScripts to align. I s
Arle Lommel wrote Thursday, December 20, 2012 8:14 AM
> NR 1.2.2 Rests currently documents how to change the default vertical
> position of multi-measure rests but not how to change the default
> vertical position of normal rests. As a result finding information about
> this functionality require
Arle, you wrote Thursday, December 20, 2012 9:58 AM
> Thanks for letting me know. If that is the process, then probably
> the documentation on how to make "small additions" itself needs
> to be updated to clarify what gets submitted where, since I was
> trying to follow the guidelines here:
>
Arle, you wrote Thursday, December 20, 2012 11:02 AM
> Given that Colin has created a new tracker do you still want me
> to submit to the LSR?
Yes please. Simply add a comment to the tracker to say what is
being done. The tracker will also remind me (or maybe others)
that the new snippet sho
Federico Bruni wrote Sunday, December 30, 2012 11:35 AM
>
> I have two different questions (quite related to each other)
>
> 1) In NR 1.2.2, Full measure rests
> The snippet multi-measure-rest-markup.ly says:
>
> "Markups attached to a multi-measure rest will be centered above or
> below it. Lo
Federico Bruni wrote Sunday, December 30, 2012 3:00 PM
> Il 30/12/2012 14:06, Trevor Daniels ha scritto:
>
>> Will you submit a revised snippet, or shall I?
>
> Please go ahead.
> I've logged in the LSR website but I cannot modify the snippets. Who
> said that w
Thomas Morley wrote Sunday, December 30, 2012 3:21 PM
> If there's need to alter a LSR-snippet I could do it for you. Please
> send me revised version.
>
> BTW, you can alter LSR-snippets yourself, only if you have the
> permission to do so.
Thanks, Harm, but I've already done it. It was my sn
Federico, you wrote Sunday, December 30, 2012 10:59 PM
> In NR 1.2.3, Upbeats:
>
> """
> So \partial 8 becomes:
>
> \time 3/4
> \set Timing.measurePosition = #(ly:make-moment -1 8)
> e8 | a4 c8 b c4 |
>
> _The property measurePosition contains a rational number indicating how
> much of the m
David Kastrup wrote Friday, January 04, 2013 8:21 AM
> Oscar Dub writes:
>>
>> From a user perspective, I thought it might be nice for the compiler
>> to send out some kind of error or warning message. Currently there's
>> no sign of anything wrong except the final output. Is this valid
>> enoug
David Kastrup wrote Friday, January 04, 2013 9:15 AM
> "Trevor Daniels" writes:
>
>> David Kastrup wrote Friday, January 04, 2013 8:21 AM
>>
>>> Oscar Dub writes:
>>>>
>>>> From a user perspective, I thought it might be nice fo
Federico Bruni wrote Sunday, January 06, 2013 6:16 PM
>I found three problems in the section "Setting automatic beam":
>
> 1) Can/Must confusion
>
> """
> If a common time signature is being used, beamExceptions must be
> disabled to enable beatStructure to work. The \set Timing.beamException
Federico Bruni wrote Sunday, January 06, 2013 4:34 PM
> Il 06/01/2013 17:07, Trevor Daniels ha scritto:
>>> NR 1.2.6, Grace notes, section Known problems:
> Anyway, using a note before the \acciaccatura block in the example would
> make it more clear?
>
> \versi
@bug squad
Could you please raise an issue to enhance the documentation to include
the information in Nicolas's reply below. Thanks.
Trevor
- Original Message -
From: "Nicolas Sceaux"
To: "Christopher R. Maden"
Cc:
Sent: Saturday, January 12, 2013 10:50 AM
Subject: Re: Book title sh
Eluze suggested:
> what about using a simple \pageBreak after the book's header?
>
> \book {
> \header {title = "…"}
> \pageBreak
> \bookpart {
>
> I feel this is clearer than relying on the following construct (from NR):
>
> "Use the breakbefore variable inside a \header block that is its
Nick Payne wrote Monday, January 14, 2013 7:46 AM
> If I use the define fonts example in the documentation at
> http://lilypond.org/doc/v2.17/Documentation/notation/fonts#entire-document-fonts
>
> to change the document fonts, the noteheads swell so that they no longer
> fit between the staf
Trevor Daniels wrote Monday, January 14, 2013 12:17 PM
>
> Nick Payne wrote Monday, January 14, 2013 7:46 AM
>
>> If I use the define fonts example in the documentation at
>> http://lilypond.org/doc/v2.17/Documentation/notation/fonts#entire-document-fonts
>>
>
David Kastrup wrote Saturday, January 19, 2013 9:10 AM
> Nick Payne writes:
>
>> BTW, both #(ly:make-moment 1 4) and #(ly:make-moment 1/4) are valid,
>>
>> Is one form preferred over the other? If so, maybe that should be
>> consistently used throughout the documentation.
>
> At any rate, due
James wrote Wednesday, February 20, 2013 8:01 AM
> On 20 February 2013 07:56, ArnoldTheresius wrote:
>
>> Miguel Jesus wrote
>> >
>> > I couldn't get it to compile even when I try to compile th whole score.
>> >
>> have you allready tried to tune lilyponds (scheme's) memory usage with the
>> env
David Kastrup wrote Sunday, March 17, 2013 9:03 AM
> Well, \relative is a music function that leaves behind absolute music.
> So if you have
>
> melody = \relative { ... \tag ... \tag ... }
>
> then \melody contains only absolute music and
>
> \removeWithTag #'xxx \melody
>
> will work fine.
Werner LEMBERG wrote Friday, March 22, 2013 1:31 PM
>
>> See below. In 2.16.2, the fingering indications are vertically
>> aligned. In 2.17.14, they aren't.
>>
>> \relative f'' {
>> \set fingeringOrientations = #'(left)
>> 4
>> }
>
> Do you consider this a bug? Actually, I like the new beh
Phil, you wrote Monday, April 08, 2013 3:25 PM
> As far as I'm aware, point and click doesn't, and can't, work on Windows.
> See
> http://lilypond.1069038.n5.nabble.com/Point-and-Click-does-not-work-on-Windows-td115986.html
>
> for details. I'd like to raise a bug report for this, so that I c
Urs Liska wrote Monday, April 15, 2013 2:38 PM
> When trying to build a documentation section with
> scripts/auxiliar/doc-section.sh I encounter a problem for which I can't
> provide a patch myself:
This script is rather installation-dependent. I've been using it for some
time (indeed I wrot
Urs Liska wrote Monday, April 15, 2013 5:07 PM
>> I have the impression that (with my previous patch about .itely and
>> .itexi files) doc-section.sh should work with both, and it should be
>> possible to completely remove cg-section.sh (and of course update the
>> doc).
>>
>> If you think tha
In the chords below, the tie between the g's is misplaced when the
direction is chosen automatically, but is correct when the direction
is manually specified.
\version "2.17.15"
\relative c' {
% The tie between the g's is misplaced
~
% Manually forcing ties up or down or adding another no
Urs, you wrote Monday, April 15, 2013 5:07 PM
> OK, what the heck:
> Here is a patch trying to fix the lilypond-book issue in doc-section.sh,
> along with a comment in the CG.
> If I have time I'll look into the other BUILD_DIRECTORY dependencies.
> And if you can confirm my impression I would a
Urs, you wrote Thursday, April 18, 2013 2:49 PM
> I will look into it (when I have time) and see if I can manage to make
> the script independent from a present build.
> It's just an interesting topic and I'll learn something from it.
> I suggest you can just wait if I provide something new.
OK
Urs, you wrote Thursday, April 18, 2013 4:07 PM
> Does that mean that it is 'lilypond-book' on Linux and
> 'lilypond-book.py' on Windows?
I don't have a Linux installation to hand to check, but as lilypond-book
is written in Python and is not (I think) cross-compiled in GUB to an
executable, al
>> If I had my email address clearly exposed in the project page, it
>> would be only tangentially more prone to spam than it currently is. I
>> do not oppose to show it, possibly with a minimal obfuscation such as
>> 'at' 'dot' and the like, which spambots can already decypher anyway.
My email a
Urs Liska wrote Monday, April 29, 2013 3:02 PM
> The NR (1.2.3 "Displaying Rhythms") states that time signatures "are
> printed at the beginning of a piece and whenever the time signature
> changes."
>
> But if I write
>
> music = {
> \time 3/4
> R2.*4
> \time 3/4
> R2.
> }
>
> the
Urs Liska wrote Monday, April 29, 2013 2:26 PM
>I have two problems with the doc-snippet
> http://www.lilypond.org/doc/v2.17/Documentation/snippets/rhythms#rhythms-making-an-object-invisible-with-the-_0027transparent-property
>
> a)
> I'm not sure if this snippet is adequate at all:
> I think w
Urs Liska wrote Monday, April 29, 2013 4:14 PM
> Am 29.04.2013 16:57, schrieb Trevor Daniels:
>> This snippet is in the LSR, so changes should be made by amending the
>> snippet there, otherwise it remains wrong in the LSR.
>
> Do I recall correctly having read that _n
Urs Liska wrote Monday, April 29, 2013 3:50 PM
> Am 29.04.2013 16:46, schrieb Trevor Daniels:
>
>> Urs Liska wrote Monday, April 29, 2013 3:02 PM
>>
>>> The NR (1.2.3 "Displaying Rhythms") states that time signatures "are
>>> printed at the b
Peter Toye wrote Monday, May 13, 2013 9:37 AM
> Lilypond crashes out when I use the "%e" format in a header
> (I'm allergic to
> leading zeroes). This is under Windows 7 Home Premium. Postings on the
> Lilypond mailing list indicate that
> this is specific to Windows - and it
> works OK on Linu
Mark Polesky wrote Thursday, July 11, 2013 5:35 AM
> Actually, I would say the vast majority of scheme functions
> in that list ought to have clearer docstrings:
> http://lilypond.org/doc/v2.17/Documentation/internals/scheme-functions
>
> Again, what's the protocol here, should I wait for someon
"Phil Holmes" wrote in message
news:kt58ju$3le$1...@ger.gmane.org...
> For one or two of the builds, it appears that the tail is placed
> in front of the whiteout box, for reasons I don't understand, although I do
> remember Keith saying that the order of placing whiteout and other grobs is
Eluze wrote Monday, July 29, 2013 12:42 PM
> Trevor Daniels wrote
>> The order in which grobs _in the same layer_ are placed is indeterminate,
>> but this can be controlled by setting the 'layer property. See
>>
>> http://www.lilypond.org/doc/v2.17/Documentatio
>> I propose that we remove string addition from assignments. It's
>> unlikely anybody was aware of it in the last 10 years, and it's not
>> like it is documented.
>
> +1
+1
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.
The message below, posted on the user list, contains a useful list of problems
encountered
while learning and using LilyPond for a significant project. Some suggest
improvements to the
documentation are needed; others could be turned into requests for
enhancements. I wonder
if the bug squad
Federico Bruni wrote Sunday, September 29, 2013 3:33 PM
> 2013/9/29 David Kastrup
>
>> Federico Bruni writes:
>>
>> > for the record, I've solved by adding a double backslash in the italian
>> > file, as suggested here:
>> > http://lists.gnu.org/archive/html/lilypond-devel/2008-08/msg00206.htm
"pls" wrote Friday, October 11, 2013 4:26 PM
Hm, but why are there line breaks after every R1? e.g.:
R1*12
r2 r4 r8 r16 r32 r64 r128 r128
It's due to the artificial nature of this example. LP tries to estimate a
suitable spacing for the section of music presented, based on the shortest
durat
> Neither am I :)
This output looks correct to me. In the first example you're asking for a
g16 to be displayed but for its duration to be 7/16 long followed by a fis16
with duration 5/16, so filling the bar. See
http://www.lilypond.org/doc/v2.17/Documentation/notation/writing-rhythms#scaling-
Federico Bruni wrote Sunday, December 15, 2013 10:45 AM
> http://lilypond.org/doc/v2.17/Documentation/usage/an-example-of-a-musicological-document.html
>
> Below the Input section there is:
>
> Documents for \verb+lilypond-book+ may freely mix music and text.
>
> \verb+ is intended? It's insi
Arjen Bax wrote Sunday, December 15, 2013 2:48 PM
> Complete minimal working example, omitting the lower staff:
>
> \version "2.16.2"
>
> sopTxt = \new Lyrics = sopL \with { alignAboveContext = "upper" }
>\lyricsto sop \lyricmode { A C }
>
> sopV = \relative c'' { << { c2 c } { \sopTxt
Urs Liska wrote Tuesday, December 17, 2013 9:01 AM
> However I noticed a behaviour I wouldn't have expected:
>
> Try out the following snippet:
>
> soprano = \relative c' { c e g c }
> verse = \lyricmode { This is my song }
>
> \score {
> \new Staff <<
> %\soprano
> { \oneVoice r4.
Urs, you wrote Tuesday, December 17, 2013 10:50 AM
> What about changing that to
> "For example, arbitrary notes in the NullVoice may arbitrarily move
> rests or cause accidentals to appear (or disappear) on the staff."
> ?
I see David's already had some thoughts about this and has raised
an is
The description of \defineBarLine in NR 1.2.5 does
not make it clear that the parameter called bartype
doubles as both the name of the barline being defined
and the definition of the bar line to be used in
the middle of the line (i.e. not at the beginning or
the end.)
The Scheme code, which trea
Keith OHara wrote Tuesday, December 31, 2013 6:14 AM
> Trevor Daniels treda.co.uk> writes:
>
>> The description of \defineBarLine in NR 1.2.5 does
>> not make it clear that the parameter called bartype
>> doubles as both the name of the barline being defined
>&
Forwarding to bug list ...
- Original Message -
From: "Peter Crighton"
To: "LilyPond Mailing List"
Sent: Wednesday, January 15, 2014 10:27 PM
Subject: Error in documentation
Hello all,
in the documentation about percussion notation it is said that you need to
include the Parenthesis_e
David Kastrup wrote Thursday, January 16, 2014 5:47 AM
> Just pushed a fix for the parenthesis engraver to staging. The chord
> bracket stuff was already fixed shortly before:
>
> commit 4bdb9204b1b682b38bd76afc03e5d629621428f1
> Should cherry-pick into translation, I think, so that this moves
This has been fixed already.
Trevor
Phil Holmes wrote Thursday, January 16, 2014 3:25 PM
> Copying to -bugs for an issue.
- Original Message -
From: Peter Crighton
To: LilyPond Mailing List
Sent: Wednesday, January 15, 2014 10:27 PM
Subject: Error in documentation
Hell
James wrote Saturday, February 01, 2014 10:51 AM
> On 01/02/14 10:14, Eluze wrote:
>> add \single, \temporary \undo and more to the index - is that worth an
>> entry in the tracker!?
> A tracker? I'd just create a patch and submit it (and create the tracker
> with git-cl for that patch). Oth
James wrote Tuesday, February 25, 2014 5:58 AM
> On 24/02/14 21:18, Paul Morris wrote:
>> The example given here:
>> http://lilypond.org/doc/v2.18/Documentation/notation/explicit-breaks
>
> While not addressing your suggestion directly, but being one of the few
> doc editors I am not sure this p
Paul Morris wrote Tuesday, February 25, 2014 7:44 PM
> That means that this statement is potentially misleading:
>
> "Lily sometimes rejects explicit \break and \pageBreak commands. There are
> two commands to override this behavior:"
Well, Lily does sometimes reject explicit breaks, for exampl
Pierre Perol-Schneider wrote Tuesday, April 08, 2014 8:45 PM
> After a discussion on the french forum I've added this snippet to the LSR:
> http://lsr.di.unimi.it/LSR/Item?u=1&id=912
>
> I think it would be helpfull to add it in the doc :
> http://lilypond.org/doc/v2.18/Documentation/notation/sp
Simon Albrecht wrote Thursday, May 29, 2014 11:43 AM
> http://www.lilypond.org/doc/v2.18/Documentation/learning/real-music-example
>
> Rereading this, I notice that the "Moderato" marking in the example would
> probably be more accurately and straightforwardly coded as
>
> \tempo "Moderato"
> be
Trevor Daniels wrote Thursday, May 29, 2014 4:50 PM
>
> Simon Albrecht wrote Thursday, May 29, 2014 11:43 AM
>
>> http://www.lilypond.org/doc/v2.18/Documentation/learning/real-music-example
>>
>> Rereading this, I notice that the "Moderato" marking in t
Janek Warchoł wrote Monday, July 28, 2014 10:12 PM
> 2014-07-28 22:51 GMT+02:00 David Nalesnik :
>
>> I think that this should be made clear in the documentation, if you haven't
>> already done this!
>
> Yes, i should do this (or maybe some doc editor would like to help me?
> I would prefer to
Timothy Lanfear wrote Sunday, August 24, 2014 8:06 PM
> Notation reference section 2.1.6. The example illustrating the use of
> addInstrumentDefinition sets instrumentTransposition context properties
> incorrectly. The midi output for Kaspar is an octave too low. The
> transposition for Melchior
Hi Tony
Could you please say which version of LilyPond you are using, so we can be sure
we're looking at the right code.
And then please enter the command "python" (without the quotes of course) at
the Command Prompt and say what the output is. You can then enter "CTRL-Z"
"Enter" to get you
Missed copying this to bug-lilypond ...
- Original Message -
From: "Trevor Daniels"
To:
Sent: Saturday, October 11, 2014 11:28 PM
Subject: Re: LilyPond - Can't get convert-ly to work
> Tony
>
> OK, thanks. It seems you have a more recent version of t
python.exe" "C:/Program
Files/LilyPond/usr/bin/convert-ly.py" -h
If this works at least you can execute it in the directory containing the
LilyPond source code.
As it's midnight I'm closing down for tonight. I'll check again tomorrow.
Trevor
----- Original Me
Hi Tony
You copied my instructions incorrectly, missing out "LilyPond" in the path to
"convert-ly" in all these examples.
Try again! It works here.
Trevor
- Original Message -
From: "Tony Warren"
To: "Trevor Daniels"
Sent: Sunday, October
Dan Eble wrote Wednesday, October 29, 2014 1:15 AM
Subject: Center whole note chords
>> I'm not top posting
> % I don't have an engraving reference to consult (yet), but I have a
> % hymnal here with some measures that look better than Lilypond's
> % default. I hope the experts will weigh in on
Thomas Morley wrote Saturday, November 01, 2014 12:05 PM
> Using d1*3/4\rest has a draw-back:
> The rest will change it's position, if \transpose is used.
Copying to bug list. This seems like a bug to me. Do others agree? I can't
see a relevant issue in the tracker.
Trevor
_
Should \offset work with the font-size of fingering? It doesn't seem to. The
default value is -5, so offsetting by -2 should give -7, with a size as shown
by the \override and \tweak, but both forms of \offset give 0.
{
\set fingeringOrientations = #'(left)
4
\override Fingering.font-siz
Urs Liska wrote Saturday, November 01, 2014 9:06 PM
> Am 1. November 2014 21:55:01 MEZ, schrieb Trevor Daniels
> :
>>
>>Thomas Morley wrote Saturday, November 01, 2014 12:05 PM
>>
>>> Using d1*3/4\rest has a draw-back:
>>> The rest will change it'
David Nalesnik wrote Saturday, November 01, 2014 9:46 PM
>
> On Sat, Nov 1, 2014 at 4:34 PM, Trevor Daniels wrote:
>>
>> Should \offset work with the font-size of fingering? It doesn't seem to.
>> The default value is -5, so offsetting by -2 should give -7, wi
> David Nalesnik wrote Saturday, November 01, 2014 9:46 PM
>>
>> On Sat, Nov 1, 2014 at 4:34 PM, Trevor Daniels wrote:
>>>
>>> Should \offset work with the font-size of fingering? It doesn't seem to.
>>> The default value is -5, so offsetting by
David Nalesnik wrote Saturday, November 01, 2014 10:40 PM
> Oh! You're tackling the documentation? I'm so glad to hear that :) :)
>
> I might have an example or two from when I was trying (unsuccessfully of
> course) to write something up. I think I may have been fooling with
> Beam.position
David Nalesnik wrote Saturday, November 01, 2014 10:53 PM
> On Sat, Nov 1, 2014 at 5:29 PM, Trevor Daniels wrote:
>
>> It also fails to work on Script.padding, although it's fine for
>> DynamicLineSpanner.padding.
>>
>>Is this a similar problem?
>
> Act
David Nalesnik wrote Saturday, November 01, 2014 11:53 PM
> On Sat, Nov 1, 2014 at 6:21 PM, Trevor Daniels wrote:
>
>> David Nalesnik wrote Saturday, November 01, 2014 10:53 PM
>>
>>>To work, \offset needs access to a default value--a number,
>>> number
Werner LEMBERG wrote Sunday, November 02, 2014 7:03 AM
> [release/2.19.15-1-13-gdd5a6e7]
>
> with this input
>
> \relative c' {
>8[ r ]
> }
>
> I would expect that there is at least a tiny distance between the rest
> and the sharp, but it seems that they directly touch – is this
> expec
David Kastrup wrote Sunday, November 02, 2014 7:38 AM
> "Trevor Daniels" writes:
>
>> Urs Liska wrote Saturday, November 01, 2014 9:06 PM
>>
>>> Am 1. November 2014 21:55:01 MEZ, schrieb Trevor Daniels
>>> :
>>>>
>>>>Thomas
Noeck wrote Sunday, November 02, 2014 12:46 AM
> That would be nice, but your example puts the f on the left of the upper
> note and not centralized between the staves (I am using 2.19.15).
You're right, Joram, \offset is not a solution. In fact, it seems to point to
another problem with \offs
David, you wrote Sunday, November 02, 2014 12:44 PM
> No, it's not a problem with \offset.
>
> Substitute this for the call to \offset, and you'll see that it's actually an
> issue with X-offset here:
>
> \once \override DynamicText.X-offset = #-3
Ah, sorry to cast invalid aspersions on \offse
1 - 100 of 455 matches
Mail list logo
