Ian Hulin writes:
> Hi Bertrand, Mike, David, Reinhold and everyone in the \markup rewrite
> gang,
>
> Here is a bulletin from the Guile V2 migration cave.
>
> I am currently brewing a patch for Tracer 1686.
>
> The markup facility as written is a major PITA when running with Guile
> V2, and is c
Hi Bertrand, Mike, David, Reinhold and everyone in the \markup rewrite
gang,
Here is a bulletin from the Guile V2 migration cave.
I am currently brewing a patch for Tracer 1686.
The markup facility as written is a major PITA when running with Guile
V2, and is currently blocking progress on this
On Oct 24, 2011, at 8:57 AM, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> \markup { \column { \italic foo bar }} would use line as its layout
>> manager and have two elements, one markup that used nothing as its
>> layout manager (markups with 1 element cannot have layout managers
"m...@apollinemike.com" writes:
> \markup { \column { \italic foo bar }} would use line as its layout
> manager and have two elements, one markup that used nothing as its
> layout manager (markups with 1 element cannot have layout managers)
> and had no transformations and one markup that used no
On Oct 23, 2011, at 11:26 PM, d...@gnu.org wrote:
> Reviewers: Bertrand Bordage,
>
> Message:
> On 2011/10/23 21:08:09, Bertrand Bordage wrote:
>> LGTM. You'll be happy to know that Mike and I are currently trying to
> get rid
>> of \markuplines, so that there will only be a \markup command.
>
Reviewers: Bertrand Bordage,
Message:
On 2011/10/23 21:08:09, Bertrand Bordage wrote:
LGTM. You'll be happy to know that Mike and I are currently trying to
get rid
of \markuplines, so that there will only be a \markup command.
No, I am not happy, since for example fret markings in tabulatur
LGTM. You'll be happy to know that Mike and I are currently trying to
get rid of \markuplines, so that there will only be a \markup command.
http://codereview.appspot.com/5312050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gn
