Re: backslashes in macro arguments

2010-06-15 Thread Karl Berry
Hi All, Changing \t to \\t ... results in a doubled-up \\ in pdf output. I'll see if I can fix that. It is twisty TeX. Trying to use @backslash{}t failed, because there is no @backslash command (should there be?). Conceivably, but it wouldn't really help you now if we added it, sin

Re: AC_FUNC_STRTOD

2010-06-15 Thread Paolo Bonzini
On 06/14/2010 09:56 PM, Bruno Haible wrote: At this point, it would be a good idea to mark all AC_FUNC_* macros that request an AC_LIBOBJ replacement as obsolete and refer the user to Gnulib for both the macro and the workaround code (and the documentation). Except maybe AC_FUNC_MALLOC and AC_FUN

Re: backslashes in macro arguments

2010-06-15 Thread Eric Blake
On 06/14/2010 09:27 PM, Ralf Wildenhues wrote: > * Eric Blake wrote on Mon, Jun 14, 2010 at 11:30:46PM CEST: >> Any other ideas for a workaround that works for both info and pdf? > > Not using macros here? Rather obvious, now that you mention it. > > -...@defmac m4_split (@var{string}, @dvar{r

Re: Autotest: ChangeLog search expensive

2010-06-15 Thread Paolo Bonzini
On 06/14/2010 11:23 PM, Ralf Wildenhues wrote: The Autotest testsuite startup code searching for ChangeLog files below the source tree is potentially very expensive. Not sure what the best way out is here, maybe some way to allow the developer to set a fixed string at `make dist' time, or allow