On 1-Apr-06, at 11:58 PM, Paul Scott wrote:
|direction| (direction):
|1|
Up or down, left or right?
The new reader wouldn't know that 1 was UP and -1 was DOWN and 0 was
in the middle. Also LEFT and RIGHT are the same as DOWN and UP,
respectively.
Ok, thanks. Fixed in CVS.
- Graham
On 2-Apr-06, at 7:25 AM, Dave K. wrote:
As far as I can tell there is no flush left/flush right
option in Lilypond,
Yes there is; see the documentation for Text marks and/or Rehearsal
marks. They're in chapter 8.
Yes, I know I can manually align every single
symbol I markup, but that shou
Rick Hansen (aka RickH) wrote:
Here is a work-around that I'm using for now:
\override Score.RehearsalMark #'break-align-symbol = #'clef
\mark \markup{ \hspace #0 \raise #1.5 "Bossa Nova" }
Thanks, with this setting 2.8.1 behaviour is like 2.6 except at line
beginning.
Maybe it should be th
On 4-Apr-06, at 8:24 AM, Rick Hansen (aka RickH) wrote:
How do I submit bug reports and their supporting .ly and .pdf
(input/output)
documents?
You could read the manual, 5.7 Reporting bugs
Can I just send an Email to somewhere with the documents attached?
We generally prefer to have an
On 4-Apr-06, at 10:04 AM, Geoff Horton wrote:
Put this at the top of your input file:
#(ly:set-option (quote no-point-and-click))
Should this be given more prominent play in the manual? I think we've
had several questions on it of late, and you kind of have to know the
answer already to go lo
Dennis O'Toole wrote:
After upgrading to 2.8.1, I notice that the .pdf files produced are
considerable larger, on the order of about 5 to 10 times the size
formerly produced. This has a detrimental effect on my ability to
store and distribute, so much that I have to back level to 2.6
to use.
> the problem with file sizes doesn't have anything to do with point &
> click though. It's usually that people are running unpatched Ghostscript
> 8.x instead of using the GUB builds.
I don't know about that. I ran a few files through with and without that line:
With point-and-click enabled: 76
David Feuer wrote:
On 4/4/06, Geoff Horton <[EMAIL PROTECTED]> wrote:
After upgrading to 2.8.1, I notice that the .pdf files produced are
considerable larger, on the order of about 5 to 10 times the size
formerly produced. This has a detrimental effect on my ability to
store and distribute, so
On 4/4/06, Geoff Horton <[EMAIL PROTECTED]> wrote:
> > > After upgrading to 2.8.1, I notice that the .pdf files produced are
> > > considerable larger, on the order of about 5 to 10 times the size
> > > formerly produced. This has a detrimental effect on my ability to
> > > store and distribute, s
> > After upgrading to 2.8.1, I notice that the .pdf files produced are
> > considerable larger, on the order of about 5 to 10 times the size
> > formerly produced. This has a detrimental effect on my ability to
> > store and distribute, so much that I have to back level to 2.6
> > to use.
>
> Put
> After upgrading to 2.8.1, I notice that the .pdf files produced are
> considerable larger, on the order of about 5 to 10 times the size
> formerly produced. This has a detrimental effect on my ability to
> store and distribute, so much that I have to back level to 2.6
> to use.
Put this at the
After upgrading to 2.8.1, I notice that the .pdf files produced are
considerable larger, on the order of about 5 to 10 times the size
formerly produced. This has a detrimental effect on my ability to
store and distribute, so much that I have to back level to 2.6
to use.
Thank you.
_
Mats Bengtsson wrote:
Rick Hansen (aka RickH) wrote:
Here is a work-around that I'm using for now:
\override Score.RehearsalMark #'break-align-symbol = #'clef
\mark \markup{ \hspace #0 \raise #1.5 "Bossa Nova" }
I would rather use:
\once \override Score.RehearsalMark #'padding = #1.5
\mark
I'm new so please forgive me.
How do I submit bug reports and their supporting .ly and .pdf (input/output)
documents?
Can I just send an Email to somewhere with the documents attached?
If so to where?
I've learned LiliPond quicly, but am running into items that appear to be
real bugs and was t
On 4/4/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> Han-Wen Nienhuys wrote:
> It seems that I have fixed this problem on accident again in 2.8.1-2
> (without actually knowing how I did it.) -- Please have a go, YMMV.
Works for me, thanks.
___
bug-
Rick Hansen (aka RickH) wrote:
Here is a work-around that I'm using for now:
\override Score.RehearsalMark #'break-align-symbol = #'clef
\mark \markup{ \hspace #0 \raise #1.5 "Bossa Nova" }
I would rather use:
\once \override Score.RehearsalMark #'padding = #1.5
\mark "Bossa Nova"
/Mats
> I've noticed a bug in 2.9.1 (using Windows) beam heights are not
> adjusted to accommodate the height of the accidental.
>
> As can be seen in the example below the flat sign goes through the
> beam as does the natural.
That alone wouldn't qualify as a bug IMHO -- I can imagine that it
sometime
Han-Wen Nienhuys wrote:
dave k wrote:
2.8.0-5 fortunately fixed the problem of Lilypond running slowly on
Windows
(having to recreate the font cache every time), but this problem has
returned in
2.8.1-1.
Yes, I can verify. Unfortunately, I'm a bit flabbergasted about why it
fell over once
Hi Everyone,
I've noticed a bug in 2.9.1 (using Windows) beam heights are not adjusted to
accommodate the height of the accidental.
As can be seen in the example below the flat sign goes through the beam as
does the natural.
I've also noticed an interesting item in the last beamed group. The pre
Hi,
I haven't had the time to catch up with all the bugs that have been reported
over the past few weeks. This is largely because of Real Life issues (i.e., I
haven't had time). Furthermore, I will start a new job next week, which will
further restrict my lilypond time.
I have concluded that t
20 matches
Mail list logo
