Re: guilev2 problem (user-markup-command sometimes not accepted)

2018-11-12 Thread David Kastrup
Thomas Morley writes: > Am Mo., 12. Nov. 2018 um 12:22 Uhr schrieb David Kastrup : >> >> Well, it's basically that macros run less synchronously with the rest >> in Guilev2 compared to Guilev1. That's because they are no longer an >> entity of their own but rather a variation on syntax

Re: guilev2 problem (user-markup-command sometimes not accepted)

2018-11-12 Thread Thomas Morley
Am Mo., 12. Nov. 2018 um 12:22 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am Mo., 12. Nov. 2018 um 10:33 Uhr schrieb David Kastrup : > > > >> Because it only compiles a reference to the symbol binding of > >> make-dummy-markup. That the symbol gets its value later is not a > >>

Re: guilev2 problem (user-markup-command sometimes not accepted)

2018-11-12 Thread David Kastrup
Thomas Morley writes: > Am Mo., 12. Nov. 2018 um 10:33 Uhr schrieb David Kastrup : > >> Because it only compiles a reference to the symbol binding of >> make-dummy-markup. That the symbol gets its value later is not a >> problem. That's the reason most of Guilev2's separate >>

Re: guilev2 problem (user-markup-command sometimes not accepted)

2018-11-12 Thread Thomas Morley
Am Mo., 12. Nov. 2018 um 10:33 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am So., 11. Nov. 2018 um 21:14 Uhr schrieb David Kastrup : > >> > >> David Kastrup writes: > >> > >> > I think that Guilev2 may do the syntax form expansion concerning > >> > "markup" before executing the

Re: guilev2 problem (user-markup-command sometimes not accepted)

2018-11-12 Thread David Kastrup
Thomas Morley writes: > Am So., 11. Nov. 2018 um 21:14 Uhr schrieb David Kastrup : >> >> David Kastrup writes: >> >> > I think that Guilev2 may do the syntax form expansion concerning >> > "markup" before executing the define-markup-command when both are >> > contained in one begin form.

Re: guilev2 problem (user-markup-command sometimes not accepted)

2018-11-12 Thread Thomas Morley
Am So., 11. Nov. 2018 um 21:14 Uhr schrieb David Kastrup : > > David Kastrup writes: > > > Thomas Morley writes: > > > >> Hi, > >> > >> the following works fine with current master (and every tested > >> lily-version): > >> #(begin > >> (define-markup-command (dummy layout props arg) (markup?)

Re: guilev2 problem (user-markup-command sometimes not accepted)

2018-11-11 Thread David Kastrup
David Kastrup writes: > Thomas Morley writes: > >> Hi, >> >> the following works fine with current master (and every tested lily-version): >> #(begin >> (define-markup-command (dummy layout props arg) (markup?) >>(interpret-markup layout props arg)) >> (display-scheme-music (markup

Re: guilev2 problem (user-markup-command sometimes not accepted)

2018-11-11 Thread David Kastrup
Thomas Morley writes: > Hi, > > the following works fine with current master (and every tested lily-version): > #(begin > (define-markup-command (dummy layout props arg) (markup?) >(interpret-markup layout props arg)) > (display-scheme-music (markup #:dummy "foo"))) > #(display "whatever")

guilev2 problem (user-markup-command sometimes not accepted)

2018-11-11 Thread Thomas Morley
Hi, the following works fine with current master (and every tested lily-version): #(begin (define-markup-command (dummy layout props arg) (markup?) (interpret-markup layout props arg)) (display-scheme-music (markup #:dummy "foo"))) #(display "whatever") With guilev2 I get: $