> What about using `$$@` (or something like that to delay expansion)
in
> the definition of `ly_progress` and omitting `Making` as an
argument,
> too? This would give
>
> $(call ly_progress,)
Too rigid. [...]
Ok.
https://codereview.appspot.com/557080043/
___
On 2019/10/05 13:44:54, lemzwerg wrote:
We are getting nearer, thanks :-)
What about using `$$@` (or something like that to delay expansion) in
the
definition of `ly_progress` and omitting `Making` as an argument, too?
This
would give
$(call ly_progress,)
Too rigid. You previousl
We are getting nearer, thanks :-)
The next thing I notice is that `ly_progress` is (always?) called as
$(call ly_progress,Making,$@,)
What about using `$$@` (or something like that to delay expansion) in
the definition of `ly_progress` and omitting `Making` as an argument,
too? This would gi
On 2019/10/04 23:23:19, lemzwerg wrote:
* The idea of showing the type of input file is nice; this might be a
useful
addition to showing the processing program. I'm not sure about that,
however.
I wouldn't put up much of a fight if someone demanded removing
it, but I find it helpful, especia
It should be the build directory. If you know how to achieve it
simply, I'll run a search and replace.
What about doing
$(subst $configure-builddir,,$(abspath ...))
to strip off the builddir prefix? This is untested, however
https://codereview.appspot.com/557080043/
Am Sa., 5. Okt. 2019 um 10:11 Uhr schrieb Werner LEMBERG :
>
>
> I've found some LSR inconsistencies. All of the following snippets
> are tagged as `docs' and approved but missing in the lilypond git
> repository (while present in the LSR bundle).
>
> #1033
> (customize-drumpitchnames,-drumstyl
I've found some LSR inconsistencies. All of the following snippets
are tagged as `docs' and approved but missing in the lilypond git
repository (while present in the LSR bundle).
#1033
(customize-drumpitchnames,-drumstyletable-and-drumpitchtable-in-layout-and-midi.ly)
#1069 (tam-tam-example
