;/Applications/LilyPond/LilyPond.app/Contents/Resources/Python/LilyPond.py",
> line 186, in compileMe
> shell = False)
> File
> "/Applications/LilyPond/LilyPond.app/Contents/Resources/subprocess.py", line
> 558, in __init__
> errread, errwrite)
> File
> "/A
handles
text
collisions, and this may change anytime.
You're right -- users can move the whole text around with #'padding or
#'extra-offset; we don't need \raise (in the context of an empty
string).
Example deleted in CVS.
Cheers,
- Graham
On Tuesday 05 April 2005 18.04, Erik Sandberg wrote:
> On Thursday 31 March 2005 01.47, Graham Percival wrote:
> > On 29-Mar-05, at 4:01 AM, Christian Hitz wrote:
> > > the proposed syntax for \raise does not work anymore (see [1]). The ""
> > > is discarded. I
On Thursday 31 March 2005 01.47, Graham Percival wrote:
> On 29-Mar-05, at 4:01 AM, Christian Hitz wrote:
> > the proposed syntax for \raise does not work anymore (see [1]). The ""
> > is discarded. It works with " ", but this also moves the raised text
> &
On 29-Mar-05, at 4:01 AM, Christian Hitz wrote:
the proposed syntax for \raise does not work anymore (see [1]). The ""
is discarded. It works with " ", but this also moves the raised text
to the right.
True. According to the docs, the following text should be at the sa
Hi,
the proposed syntax for \raise does not work anymore (see [1]). The ""
is discarded. It works with " ", but this also moves the raised text to
the right.
(Lily 2.5.16, MacOS X)
Christian
[1]
http://lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Text-
mar
