On 21.4.2015 14:37, Eric Blake wrote:
...
This reads a bit awkwardly; I would like to propose this alternate
wording, still in your name. If you agree, I'll go ahead and push.
Great, go ahead and fix the wording.
Oh, and I just noticed that we don't document the two-arg form; the
On 04/21/2015 06:51 AM, Matěj Týč wrote:
On 21.4.2015 14:37, Eric Blake wrote:
...
This reads a bit awkwardly; I would like to propose this alternate
wording, still in your name. If you agree, I'll go ahead and push.
Great, go ahead and fix the wording.
Done. Thanks again for your first
On 03/17/2015 06:13 PM, Matěj Týč wrote:
Hello,
the subject says it all, m4 allows you to define and/or undefine macros,
so if one uses it e.g. in Makefiles, it is easy to alter the output.
However, m4 is a real pain to use, m4sugar is so much better. But
autom4te, the convenient m4sugar
On 04/15/2015 04:58 PM, Eric Blake wrote:
Based on an idea by Bernhard Reutner-Fischer.
We frequently used the idiom of 'test ${var+set} = set' to
test if $var was set to a non-empty string, but this can portably
be trimmed to a more compact 'test ${var+y}' for a smaller
configure file.
On 04/16/2015 03:00 PM, Matěj Týč wrote:
Hello,
I attach the suggestion of autoconf m4sugar-related documentation
improvement.
Specifically, the patch adds a more concrete description of what the
m4_pattern_forbid thingy that pretends it is a macro accepts as an
argument.
Thanks for the
