Martin Tarenskeen wrote:
the standard for starting a program once it's installed is to call the
program from the command-line. precompiled packages generally install to
/usr/bin, self-compiled packages to /usr/local/bin or on some
distributions to /opt/bin or /opt/local/bin.
Wherever
Le 26 avr. 09 à 05:12, Chip a écrit :
In using the sample code from NR 3.2.4 Table Of Contents I get all
my page numbers as question marks. Even the example shows all the
page numbers are page 1. There is no info on how to get the page
numbers to increment, or how to manually insert the pag
Le 26 avr. 09 à 01:38, Nick Payne a écrit :
I'm putting together a book of pieces, and using a particular font for
headers, footers, titles, subtitles, etc. The one place where I
haven't
figured out how to get that font used is for the header text for the
table
of contents that Lilypond crea
On Sat, Apr 25, 2009 at 01:36:11PM -0600, Carl D. Sorensen wrote:
>
> On 4/25/09 1:31 PM, "Neil Puttock" wrote:
>
> > Perhaps the point I was trying to make got lost in my slightly
> > facetious reply: if we're talking about LSR snippets which are in the
> > docs, the LSR editor must be mindful
Dear community,
with Your hints I made success with my idea of changing the enharmonic context.
But, what I did doesn't still work like I expect it.
Here is an example with short comments on it:
\version "2.13.0"
#(define (naturalize-pitch p)
(let* ((o (ly:pitch-octave p))
(a (* 4 (ly
I'm putting the finishing touches on a book of English folk tunes, but
have a few problems.
The first is in trying to center a footnote. So far, I've got this:
\paper {
#(define page-breaking ly:minimal-breaking)
ragged-bottom = ##t
oddFooterMarkup = \markup { Engraved on
Graham Percival wrote Saturday, April 25, 2009 12:53 PM
On Sat, Apr 25, 2009 at 12:31:14PM +0100, Trevor Daniels wrote:
Graham Percival wrote Saturday, April 25, 2009 10:13 AM
Eh?!?! You want to tell people to put articulation and dynamic
marks after the duration, before they've been told
2009/4/26 Graham Percival :
> This is easily solved; the python script that copies from
> input/new/ to input/lsr/ should add a "This snippet only works in
> 2.13"; that way, the LSR editor can easily see such snippets from
> browsing the docs.
We already have a comment which says where the snipp
Mark Austin wrote:
I'm putting the finishing touches on a book of English folk tunes,
but have a few problems.
I suppose it's rather crude, but I like using \null for things like this.
So, for the footer:
\markup { Engraved ... }
becomes
\markup \fill-line { \null \line
Hello.
I am transcribing a music that defines the time signature as
(2-3)/4
That is, some bars are 2/4, some others are 3/4.
While I can change time signature from time to time accordingly with the
composer changes, that polutes a lot the music score.
Any suggestion on a solution?
Thank you
A
Alberto Simões wrote:
Hello.
I am transcribing a music that defines the time signature as
(2-3)/4
That is, some bars are 2/4, some others are 3/4.
While I can change time signature from time to time accordingly with the
composer changes, that polutes a lot the music score.
Any suggestion on
Hello, Jonathan
Jonathan Kulp wrote:
> Alberto Simões wrote:
>> Hello.
>>
>> I am transcribing a music that defines the time signature as
>>
>> (2-3)/4
>>
>> That is, some bars are 2/4, some others are 3/4.
>>
>> While I can change time signature from time to time accordingly with the
>> composer
When I conclude my addition to the LSR, do I click on the Save button or
the OK button? Does it make a difference? I just want to make sure I
don't loose my work, but that it gets properly inserted into the LSR.
Regards,
Chip
___
lilypond-user mailin
Hi,
I am writing a score for violin with many commands that are repeated and
would like to know if it is possible to write a shortcut command.
The commands are:
- \downbow
- \upbow
- ^\markup { \small "III" }
- _\markup { \italic { rit. } }
~Marc
--
View this message in context:
http:
2009/4/26 Chip :
> When I conclude my addition to the LSR, do I click on the Save button or the
> OK button? Does it make a difference? I just want to make sure I don't loose
> my work, but that it gets properly inserted into the LSR.
The only difference between the two options is that `OK' takes
Neil Puttock wrote:
2009/4/26 Chip :
When I conclude my addition to the LSR, do I click on the Save button or the
OK button? Does it make a difference? I just want to make sure I don't loose
my work, but that it gets properly inserted into the LSR.
The only difference between the two o
2009/4/25 Marc Hohl :
> Hello tablature users*,
Like Carl, I'm not a tablature user, so I can only comment on matters of coding.
Some suggestions and thoughts follow below:
> % some publications use the triangled note head
> % for palm mute, so here we go:
> palmMuteOn = { \set shapeNoteStyles =
Neil Puttock wrote:
2009/4/26 Chip :
When I conclude my addition to the LSR, do I click on the Save button or the
OK button? Does it make a difference? I just want to make sure I don't loose
my work, but that it gets properly inserted into the LSR.
The only difference between the two o
2009/4/26 Chip :
> Hmm, did run into an apparent error - after I click on the Save button I get
> a pop-up box that says "No output from Lilypond", did I do something wrong?
Probably not. :)
It normally means your snippet is incompatible with the version of
LilyPond being run on LSR (2.10.12) or
2009/4/25 Nick Payne :
> This reduction seems about right to me, comparing the sizes on the normal and
> grace notes:
Thanks, I've made the changes in git.
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailma
Neil Puttock wrote:
2009/4/26 Chip :
Hmm, did run into an apparent error - after I click on the Save button I get
a pop-up box that says "No output from Lilypond", did I do something wrong?
Probably not. :)
It normally means your snippet is incompatible with the version of
LilyPond b
Chip wrote:
Neil Puttock wrote:
2009/4/26 Chip :
Hmm, did run into an apparent error - after I click on the Save
button I get
a pop-up box that says "No output from Lilypond", did I do something
wrong?
Probably not. :)
It normally means your snippet is incompatible with the version
Hi Chip,
One more option is to place the date in the footer, or as it is
called in Lilypond - the tagline.
This is not accurate: the tagline and the footer are two different
things. (Check the docs to see what each of them are.)
Please correct the LSR snippet accordingly, so we don't have
Kieren MacMillan wrote:
Hi Chip,
One more option is to place the date in the footer, or as it is called
in Lilypond - the tagline.
This is not accurate: the tagline and the footer are two different
things. (Check the docs to see what each of them are.)
Please correct the LSR snippet accordin
Jonathan Kulp wrote:
Chip wrote:
Neil Puttock wrote:
2009/4/26 Chip :
Hmm, did run into an apparent error - after I click on the Save
button I get
a pop-up box that says "No output from Lilypond", did I do
something wrong?
Probably not. :)
It normally means your snippet is incompat
Hi Chip,
I already did [the testing]. Below is the list of tested/usable
parameters
Nice!
Thanks,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Kieren MacMillan wrote:
Hi Chip,
One more option is to place the date in the footer, or as it is
called in Lilypond - the tagline.
This is not accurate: the tagline and the footer are two different
things. (Check the docs to see what each of them are.)
Please correct the LSR snippet accordin
Chip wrote:
Thanks Jon,
I got those parameters from a Linus manpage and tested all of them and
more, and the ones listed below work as expected. There were several
others that did not work on the Lilypond output. That is why I think
these should be listed, so someone doesn't try one of the oth
Jonathan Kulp wrote:
Chip wrote:
Thanks Jon,
I got those parameters from a Linus manpage and tested all of them
and more, and the ones listed below work as expected. There were
several others that did not work on the Lilypond output. That is why
I think these should be listed, so someone does
Neil,
Thanks for your input. I think it's all really good.
On 4/26/09 1:49 PM, "Neil Puttock" wrote:
> 2009/4/25 Marc Hohl :
>> Hello tablature users*,
>
> Like Carl, I'm not a tablature user, so I can only comment on matters of
> coding.
>
> Some suggestions and thoughts follow below:
>
For chords I don't think there is a standard approach. Chords haven't
been around long enough. I was hoping to collect opinions here. :) Maybe
the best source would be in some typography book? I checked mine and
couldn't find any specific mention about the position, only the weight.
Maybe someo
31 matches
Mail list logo
