Guy Stalnaker writes:
> Add to this page after the section for Divisi lyrics at the bottom:
>
> http://lilypond.org/doc/v2.16/Documentation/notation/techniques-specific-to-lyrics
>
> The following is based on this page for Temporary polyphonic passages.
>
> http://lilypond.org/doc/v2.16/Documenta
nd. I will reluctantly agree to adding something like this
>> at the bottom of some section:
>
> Done
>
> Trevor
>
>
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
>
>
--
View this message in
Graham Percival wrote Friday, August 13, 2010 7:28 AM
On Thu, Aug 12, 2010 at 03:05:38PM -0700, -Eluze wrote:
The lilypond executable may be called as follows from the command
line.
lilypond [option]... file...[[1]>file.log] [2>file.txt]
1> and 2> (and, for the matter, &> ) have nothin
On Thu, Aug 12, 2010 at 03:05:38PM -0700, -Eluze wrote:
>
> The lilypond executable may be called as follows from the command line.
>
> lilypond [option]... file...[[1]>file.log] [2>file.txt]
1> and 2> (and, for the matter, &> ) have nothing to do with
lilypond. I will reluctantly agree to add
that direct their output to that file?
if you feel this is overloading the simple invocation used before this could
be added at the very end of this section.
--
View this message in context:
http://old.nabble.com/doc-addition%3A-the-full-lilypond-command-line-with-options%2Bredirections-tp29423
Eluze wrote Tuesday, August 10, 2010 2:54 PM
if you specify a folder name as output option the output will be
directed to
that folder and the name of the file is preserved
so i suggest the following change/addition - or similar - in the
application usage manual:
1.2 Command-line usage
Comm
On Tue, Aug 10, 2010 at 04:49:24PM +0100, Trevor Daniels wrote:
>
> Eluze wrote Tuesday, August 10, 2010 2:54 PM
>
>> if you specify a folder name as output option the output will be
>> directed to
>> that folder and the name of the file is preserved
> I don't know, but I'm reluctant to cement th
Eluze wrote Tuesday, August 10, 2010 2:54 PM
happenstance or intention?
I don't know, but I'm reluctant to cement this change
into the docs until someone confirms it is working as
intended.
Looks useful though. Thanks for pointing it out.
if you specify a folder name as output option the o
lilypond
-o,--output=FILE or FOLDER
Set the default output file to FILE. The appropriate suffix will be added
(e.g. .pdf for pdf)
if a folder of that name exists, output will be directed to FOLDER (keeping
the file name)
thanks!
--
View this message in context:
http://old.nabble.com/doc
Thanks Eluze. Edited in and pushed to git.
Trevor
- Original Message -
From: "-Eluze"
To:
Sent: Monday, August 09, 2010 5:43 PM
Subject: doc-addition for -I / --include
in AU, chapter 1.2 Command-line usage, Invoking Lilypond
http://lilypond.org/doc/v2.13/Documenta
http://old.nabble.com/doc-addition-for--I-include-tp29389836p29389836.html
Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
In the glossary of the online-documentation for 2.11, section `meter'
there are two additions it'd be worth making.
1. The UK spelling is `metre'
2. The `meter' (or metre) header line for hymn music refers to the
the arrangement of syllables into lines for the corresponding lyrics.
Metre
In the glossary, please add `stringendo'.
It means, Urging or hastening the time, as to a climax.
(webster).
It should probably cross-reference accelerando.
As I understand it, accelerando means a gradual speeding up;
stringendo a more rapid one.
--
Dr Peter Chubb http://www.gelato.unsw.edu
On 07/02/2008, Han-Wen Nienhuys wrote:
> 2008/2/7, Mats Bengtsson :
> > Keeping the description at a cookbook level, as you propose, is one
> > alternative.
Probably the worst one. :-) But a good conversation starter, I hope.
> > Another alternative is to describe more clearly what the different
2008/2/7, Mats Bengtsson <[EMAIL PROTECTED]>:
> Keeping the description at a cookbook level, as you propose, is one
> alternative.
> Another alternative is to describe more clearly what the different
> parameters
> actually mean.
So, the e-mail message that Risto cites is a bit on the obtuse side
Risto Vääräniemi wrote:
Should the Section 1.8.2 Text markup - Font selection have a text
describing how the make-pango-font-tree parameters should be used.
Something like:
If the set-global-staff-size is used for changing the global staff
size, the \myStaffSize should be set to the same
Dear All,
In 2006 Eyolf made a extensive study about the combined effect of the
set-global-staff-size and the Pango font definitions in
make-pango-font-tree [1]. It seems that this manual section has not
been yet updated. I was struggling with the same thing yesterday and
because I've got no inter
...in which case it would seem to be almost completely useless. (If it
needs to be restated after every use, then one may as well just end the
spanner manually.)
Oh yes it can be useful :
begin code %
\version "2.11.34"
music = {
c'1
\tag #'oboe \endSpanners d'1 \<
\tag #'
Mats Bengtsson wrote:
> The only "documentation" of \endSpanners available in the LilyPond
> distribution today is the regression test example called
> music-function-end-spanners.ly
>
> A quick look at the implementation reveals that the \endSpanner function
> takes one argument, which is a music
Trevor Bača wrote:
I describe the behavior below and then suggest a small doc addition to
8.1.2 "Text Spanners" at the end of this mail.
Thanks, added. I didn't include any changes from Maximilian; if you
want to clarify anything, please send another doc addition.
C
ners",
immediately before the "see also"?
%%% BEGIN DOC ADDITION %%%
The music function \endSpanners terminates spanners and hairpins after
exactly one note.
\new Staff {
\endSpanners
c'2 \startTextSpan c'2
c'2 \< c'2
}
When using \endSpanners
Trevor Bača wrote:
So that's a brief explanation of the function. Could you please insert
the following at the very bottom of 8.1.2 "Text and line spanners",
immediately before the "see also"?
%%% BEGIN DOC ADDITION %%%
The music function \endSpanners terminates sp
with trill spanners. I haven't, unfortunately, been able to produce a
definitive answer to Risto's question; *but*, I did discover a new
spanner-related music function that has somehow escaped announcement
and documentation.
I describe the behavior below and then suggest a small doc add
Trevor Bača wrote:
Could I suggest the following verbatim change to 11.1.2 "Page formatting"?
Thanks, added.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Graham,
Could I suggest the following verbatim change to 11.1.2 "Page formatting"?
There are three small changes:
1. The introduction of a "Commonly tweaked properties" section to
introduce ly/paper-defaults.ly and ly/titling-init.ly.
2. The move of the "Example" section immediately followi
Bertalan Fodor wrote:
Created as a plugin for the jEdit (http://www.jedit.org) text editor
LilyPondTool is the most feature-rich text-based tool for editing
LilyPond scores. Its features include a Document Wizard with lyrics
support to set up documents easier, and embedded PDF viewer with advance
Ok :-)
Let's make 2nd try:
Created as a plugin for the jEdit (http://www.jedit.org) text editor
LilyPondTool is the most feature-rich text-based tool for editing
LilyPond scores. Its features include a Document Wizard with lyrics
support to set up documents easier, and embedded PDF viewer with a
Bertalan Fodor escreveu:
> In section 13.6 Editor support I propose the following modifications.
>
> --
>
> - Because LilyPondTool has the most most features and generally (at
> least on Windows platforms) it requires almost no configuration, I would
> list it as the first.
> - Remove
In section 13.6 Editor support I propose the following modifications.
--
- Because LilyPondTool has the most most features and generally (at
least on Windows platforms) it requires almost no configuration, I would
list it as the first.
- Remove the jEdit part and write the followi
Cameron Horsburgh wrote:
An addition for the manual in section 10.3.1 "Creating MIDI Files"
after the second sentence
Thanks, that's perfect. Added to git.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.or
An addition for the manual in section 10.3.1 "Creating MIDI Files"
after the second sentence
[The tempo is specified using the \tempo command. In this example the
tempo of quarter notes is set to 72 beats per minute.] The tempo
specification can not take dotted note lengths as an argumen
Cameron Horsburgh wrote:
Here's a small addition for the docs. It is intended to go in Section
8.2.3 (Rehearsal marks) after the sentence "You may use
Thanks, added.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.or
Here's a small addition for the docs. It is intended to go in Section
8.2.3 (Rehearsal marks) after the sentence "You may use
format-mark-barnumbers, format-mark-box-barnumbers, and
format-mark-circle-barnumbers to get bar numbers instead of
incremented numbers or letters."
Given the overlap of su
Graham Percival escreveu:
>>> parameters to
>>> make-pango-font-tree really mean. I guess we all have just started
>>> from an
>>> example and tried to play around with it to try to figure it out.
>>
>> Yes. This is quite hazy, and also quite important, so I definitely
>> think it should be include
Eyolf Ostrem wrote:
On Thu 21 December 2006 08:56, Mats Bengtsson wrote:
See http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00351.html
for example.
Yes, that's an important bit of information to add; I cursed quite a lot
before I figured that one out...
http://lilypond.org/web/
Graham Percival wrote:
Eyolf Ostrem wrote:
Note that if you also change the default font family for the entire
document,
as described in 8.1.7 Font selection, some extra steps are needed.
Could you check the current manual about this tidbit? I confess that
I don't understand the font stu
Eyolf Ostrem wrote:
I sent this to the lilypond-devel list, but it doesn't seem to have come
through.
Thanks! However... (see below)
10.5.1 Setting global staff size:
To set the global staff size, use set-global-staff-size.
#(set-global-staff-size 14)
This sets the global default si
Markus Schneider wrote:
in "9.1.2 Setting automatic beam behavior" I'd like to propose a doc
addition regarding automatic beam behaviour for 'unusual' time signatures.
(http://lilypond.org/doc/v2.9/Documentation/user/lilypond/Setting-automatic-
beam-behavior.html#Settin
Hello all,
in "9.1.2 Setting automatic beam behavior" I'd like to propose a doc
addition regarding automatic beam behaviour for 'unusual' time signatures.
(http://lilypond.org/doc/v2.9/Documentation/user/lilypond/Setting-automatic-
beam-behavior.html#Setting-automatic-be
Markus Schneider wrote:
This also applies partially to "6.4.5 Bar lines" in the current doc.
http://lilypond.org/doc/v2.9/Documentation/user/lilypond.html#Bar-lines
Could you link to the single-node version of this page? Loading it is
much faster than loading the all-in-one page. :)
A vis
Markus Schneider wrote:
In the program reference regarding the bar-line-interface
http://lilypond.org/doc/v2.9/Documentation/user/lilypond-internals.html#bar-line-interface
there is one type of bar lines missing:
"||:"
Thanks! I have added it to the documentation.
This also applies par
In the program reference regarding the bar-line-interface
http://lilypond.org/doc/v2.9/Documentation/user/lilypond-internals.html#bar-line-interface
there is one type of bar lines missing:
"||:"
This also applies partially to "6.4.5 Bar lines" in the current doc.
http://lilypond.org/doc/v2.9/Docu
On 31-May-06, at 9:15 AM, Vaclav Smilauer wrote:
I suggest adding the following to "13.2 Integrating LaTeX and music",
as
Thanks, added! I didn't include the example graphic, due to technical
difficulties in generating the image inside the texinfo manual.
However, I think it's clear enoug
I suggest adding the following to "13.2 Integrating LaTeX and music", as
an extra feature. It would be useful for HTML and texinfo as well, but
this works for LaTeX only. Best regards,
Vaclav Smilauer
---
Sometimes, it is useful to display music elements as if they continued
after the end of th
On 22-May-06, at 4:49 AM, Cameron Horsburgh wrote:
Okay, here's an updated version of my suggested entry.
The horizontal location of rehearsal marks can be adjusted by setting
break-align-symbol:
Thanks, added to CVS.
- Graham
___
lilypond-deve
On Mon, May 22, 2006 at 08:22:48PM +1000, Cameron Horsburgh wrote:
Okay, here's an updated version of my suggested entry.
**
The horizontal location of rehearsal marks can be adjusted by setting
break-align-symbol:
\relative {
c1
\key cis \major
\clef alto
\overrid
Cameron Horsburgh schreef:
I've had a look at the note in the 2.8 News file about the new rehearsalMarkAlignSymbol.
> It seems to say everything that's needed, but I'm wondering if we need
> a list of possible values. The example shows key-signature and
clef---where can I find the others?
Che
I've had a look at the note in the 2.8 News file about the new
rehearsalMarkAlignSymbol. It seems to say everything that's needed, but I'm
wondering if we need a list of possible values. The example shows key-signature
and clef---where can I find the others?
I've also noticed that the explanati
48 matches
Mail list logo
