Hi,
>> And you have nothing in your "macro" that would actually switch the
>> "body" into markup mode. To me, that looks like being harder to explain
>> to both compiler and user.
>
> Harder to the compiler? Yes, not hard to imagine.
> To the user? I'm not sure. But that's only me.
>
> This is
2015-12-13 0:16 GMT+01:00 David Kastrup :
> Thomas Morley writes:
>
>> Though, I thought about some sort of macro, doing the job like:
>>
>> %% the macro:
>> \simple-define-markup-command
>> %% the args:
>> % name:
>> bold-red
>> % body:
>> \bold \with-color #red \etc
>>
>> I think it woul
Thomas Morley writes:
> Though, I thought about some sort of macro, doing the job like:
>
> %% the macro:
> \simple-define-markup-command
> %% the args:
> % name:
> bold-red
> % body:
> \bold \with-color #red \etc
>
> I think it would prevent some confusions.
\etc is not a "body". It's
2015-12-11 11:50 GMT+01:00 David Kastrup :
>> Having
>> \markup bold-red = <ẃhat-ever>
>> ,i.e. a definition might lead to confusions.
>
> The compiler isn't confused. The question is more about the user.
Yep, that was exactly my concern.
>> Is it possible to create a sort-of-markup-macro to be
Thomas Morley writes:
> 2015-12-10 11:58 GMT+01:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> Not sure why
>>> foo-markup = \markup \bold \with-color #cyan \markletter \etc
>>> \markup \foo #1
>>> does not work, as opposed to
>>> bold-red-markup = \markup \bold \with-color #red \etc
>
2015-12-10 11:58 GMT+01:00 David Kastrup :
> Thomas Morley writes:
>
>> Not sure why
>> foo-markup = \markup \bold \with-color #cyan \markletter \etc
>> \markup \foo #1
>> does not work, as opposed to
>> bold-red-markup = \markup \bold \with-color #red \etc
>> \markup \bold-red "text"
>
>
Thomas Morley writes:
> Not sure why
> foo-markup = \markup \bold \with-color #cyan \markletter \etc
> \markup \foo #1
> does not work, as opposed to
> bold-red-markup = \markup \bold \with-color #red \etc
> \markup \bold-red "text"
Anyway, should this rather work using the syntax
\mark
Hi David,
On Dec 10, 2015, at 1:47 AM, David Kastrup wrote:
> As a note aside: it was a hole in one. First attempt was accepted by
> the compiler and worked. For a mixed non-trivial Bison/Scheme feature…
Nicely done!
Thanks, as always, for your great work.
Cheers,
Kieren.
2015-12-10 7:47 GMT+01:00 David Kastrup :
> That's issue 4687, with patch. The
> markup grammar special-cased "markup command chain with only markup
> argument missing" and the \etc hooked into that special case. I've
> added the rest now.
>
> As a note aside: it was a hole in one. First attemp
Thomas Morley writes:
> 2015-12-09 17:17 GMT+01:00 David Kastrup :
>>
>> Why not
>>
>> \set Score.markFormat = \markup \circle \bold \markletter \etc
>>
>> (the latter use of \etc does not work yet but that's fixable).
>
> Not sure why
> foo-markup = \markup \bold \with-color #cyan \markletter
2015-12-09 17:17 GMT+01:00 David Kastrup :
> Thomas Morley writes:
>
>> 2015-12-09 15:19 GMT+01:00 David Kastrup :
>>> Thomas Morley writes:
>>>
This whole stuff looks quite obfuscated to me.
Currently we do a lot of calculation to end up with then hard-coded
vectors.
Why not
Hi all,
On Dec 9, 2015, at 11:17 AM, David Kastrup wrote:
> Why not
> \set Score.markFormat = \markup \circle \bold \markletter \etc
Gosh, that’s pretty!
(At least relatively speaking.)
Cheers,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.i
Thomas Morley writes:
> 2015-12-09 15:19 GMT+01:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> This whole stuff looks quite obfuscated to me.
>>> Currently we do a lot of calculation to end up with then hard-coded vectors.
>>> Why not give the initial value directly?
>>> Below three suggesti
On Wed, 9 Dec 2015 14:16:37 +0100
Thomas Morley wrote:
> This whole stuff looks quite obfuscated to me.
Aren't we just looking for \mark \locase \default?
I can think of many other purposes for \locase \upcase \titlecase ...
-- Johan
___
lilypond
2015-12-09 15:19 GMT+01:00 David Kastrup :
> Thomas Morley writes:
>
>> This whole stuff looks quite obfuscated to me.
>> Currently we do a lot of calculation to end up with then hard-coded vectors.
>> Why not give the initial value directly?
>> Below three suggestions, via string, char-set, vecto
Thomas Morley writes:
> This whole stuff looks quite obfuscated to me.
> Currently we do a lot of calculation to end up with then hard-coded vectors.
> Why not give the initial value directly?
> Below three suggestions, via string, char-set, vector.
> Maybe we could even introduce a context-prope
2015-12-09 12:52 GMT+01:00 Andrew Bernard :
> Hi Abraham,
>
> Well, as a very quick hack, you can change the uppercase hardwired A in this
> code to lowercase hardwired as below. I am not suggesting this is the best
> solution, but it works.
>
> Andrew
>
>
>
> — snip
>
> define-markup-commands.scm
Hi Abraham,
Well, as a very quick hack, you can change the uppercase hardwired A in this
code to lowercase hardwired as below. I am not suggesting this is the best
solution, but it works.
Andrew
— snip
define-markup-commands.scm
(define number->mark-letter-vector (make-vector 25 #\a))
(d
At 09:34 09/12/2015 +0100, Urs Liska wrote:
Am 09.12.2015 um 08:57 schrieb Brian Barker:
At 17:08 08/12/2015 -0700, Abraham Lee wrote:
I am trying to figure out how to make rehearsal mark letters be
their lower-case counterparts. I've read through all the options
in "scm/translation-functions.
Am 09.12.2015 um 08:57 schrieb Brian Barker:
> At 17:08 08/12/2015 -0700, Abraham Lee wrote:
>> I am trying to figure out how to make rehearsal mark letters be their
>> lower-case counterparts. I've read through all the options in
>> "scm/translation-functions.scm" to see what's currently availab
At 17:08 08/12/2015 -0700, Abraham Lee wrote:
I am trying to figure out how to make rehearsal mark letters be
their lower-case counterparts. I've read through all the options in
"scm/translation-functions.scm" to see what's currently available
and it doesn't seem to be an option at the moment.
Greetings, All!
I am trying to figure out how to make rehearsal mark letters be their
lower-case counterparts. I've read through all the options in
"scm/translation-functions.scm" to see what's currently available and it
doesn't seem to be an option at the moment.
I realize this isn't the standar
22 matches
Mail list logo
