Exactly what commands (including all the options) do you use?
/Mats
Quoting Graeme McKinstry graeme.mckinstry at xtra.co.nz:
First some information
Lilypond 2.11 running under Mac OS X 10.4.9 (Intel)
Lilypond installed and running fine. Generating PDF output.
Problem:
Graham Percival gpermus at gmail.com writes:
What about giving a StaffGroup some width? I'm thinking of your recent
fix for #352. I mean, if there's a StaffGroup grob then we want the bar
numbers to be higher; if there's no StaffGroup grob then we don't want
to move the bar numbers.
Of
Graeme McKinstry wrote:
(lilypond taken from the manual). Saved as lily_music.pdftex
From the terminal window:
lilypond-book --format=latex --pdf ~/lily_music.pdftex
What about simply naming the file .lytex and doing
lilypond-book file.lytex
I recommend trying a simple, default-option
I begin to suspect that you have some problems with character encoding or
line endings in the text file. Do you, by chance, use old-style Mac
line-endings
(i.e. just a CR)? In that case, try to save the file using the new Mac OS X
convention (which is the same as UNIX has always been using) to
Mario Colbert wrote:
Dearest Lilypond mailing list:
Hello. Although I've had lilypond installed since June of 2006, I have
not tried to put anything substantial in there. However, after having
to put together a nice set of good-looking scores of my own
composition for percussion, I've
The solution for this is to use more accurate glyph outlines than
bounding boxes. I hope to do this at some point, but it is
non-trivial.
Making metafont emit improved data on glyph outlines is quite easy.
The very question is *what* shall it emit...
Can you elaborate on this?
Werner
Mats Bengtsson mats.bengtsson at ee.kth.se writes:
I begin to suspect that you have some problems with character encoding or
line endings in the text file. Do you, by chance, use old-style Mac
line-endings
(i.e. just a CR)? In that case, try to save the file using the new Mac OS X
Have you read the section called Notes for the MacOS X app in the manual?
/Mats
Graeme McKinstry wrote:
Mats Bengtsson mats.bengtsson at ee.kth.se writes:
I begin to suspect that you have some problems with character encoding or
line endings in the text file. Do you, by chance, use
Mats Bengtsson mats.bengtsson at ee.kth.se writes:
Have you read the section called Notes for the MacOS X app in the manual?
/Mats
I have read the notes, but I am using
a different shell (tsch and not bash).
I have got the exec part to work, but I can't get
the path name to be
Graeme McKinstry wrote:
I have got the exec part to work, but I can't get
the path name to be global. I think the manual is
for bash.
It is indeed; bash is standard in OSX 10.3 and 10.4. Why change it?
setenv PATH ~/bin:$PATH
but I am not an expert and so I do not know if this
is the
The .profile file is specific for bash. If you use tcsh, you should do
the initialization
in a file called .tcshrc or .cshrc (at least on Linux/UNIX, I don't know
anything in
specific about Mac OS). I hope you first have verified that it works to
manually
do
setenv PATH ~/bin:$PATH
in your
On Monday 23 April 2007 14:38, Werner LEMBERG wrote:
The solution for this is to use more accurate glyph outlines than
bounding boxes. I hope to do this at some point, but it is
non-trivial.
Making metafont emit improved data on glyph outlines is quite easy.
The very question is *what*
On Monday 23 April 2007 09:23, Graham Percival wrote:
Joe Neeman wrote:
On Monday 23 April 2007 05:49, Maximilian Albert wrote:
Reinserting the above line manually in scm/define-grobs.scm and
comparing it with Mats' solution yields exactly the same result for
staves with brackets, but for
It would be the coolest if (all) these extensions could happen in
grob-property space.
This could be done by automatically overriding and reverting grob
properties when middleCPosition or tonic context properties change.
2007/4/21, Kevin Dalley [EMAIL PROTECTED]:
As another step toward in my
Making metafont emit improved data on glyph outlines is quite
easy. The very question is *what* shall it emit...
Can you elaborate on this?
If it could emit a list of line segments that approximates the
boundary of the glyph, that would be _very_ useful.
Please take an arbitrary
Jack -
You might find the postings at http://partoches.bearteam.org/ useful. There
is a link to ly source files near the bottom of the page.
- Bruce
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jack Cooper
Sent: Sunday,
Marcus -
Lily gets lost and throws in the towel when curly braces aren't correct.
Trivially, a single c fails while {c} is O.K.
- Bruce
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Marcus Macauley
Sent: Tuesday, October 10,
On Tuesday 24 April 2007 00:39, Werner LEMBERG wrote:
Making metafont emit improved data on glyph outlines is quite
easy. The very question is *what* shall it emit...
Can you elaborate on this?
If it could emit a list of line segments that approximates the
boundary of the glyph,
Hi all.
I have been trying to set an analysis of MacDowell's To a Wild Rose on
lilypond. After a whole heap of time getting to know lily better and
heaps of time scrounging through the manuals and the snippet repository,
I've pretty much got it together but for one final detail.
I have placed my
Hi, Tiago and Bruce:
Not pretty, but:
Nice! Another option (slightly inferior, but somewhat simpler) is
YYY = \markup { \combine underlined markup \translate #'(0 . -0.3)
__ }
{ c''^\YYY }
Hope this helps!
Kieren.
___
20 matches
Mail list logo
