Paul Eggert wrote:
> > I would suggest to entirely remove the Makevars handling from 'bootstrap',
> > and instead let the maintainers create a Makevars file by hand, according
> > to the documentation - like they also create configure.ac and Makefile.am
> > files by hand.
>
> Sounds good to me; is
James Youngman wrote:
Do the gnulib maintainers feel that the creation of the
FTW_MOUNT/FTW_XDEV dichotomy in POSIX nftw() justifies an analogous
thing in fts()?
Yes, that sounds right.
Bruno Haible wrote:
I would suggest to entirely remove the Makevars handling from 'bootstrap',
and instead let the maintainers create a Makevars file by hand, according
to the documentation - like they also create configure.ac and Makefile.am
files by hand.
Sounds good to me; is that a trivial
Hi Paul,
Tim Rühsen tells me that one of the problems he had yesterday with Makevars
is that 'bootstrap' overwrites po/Makevars with one that substitutes values
from bootstrap.conf.
This has several drawbacks:
* In the gettext documentation, Makevars is documented [1] as a file that
the mai
Eric mailed the findutils list a while back to point out that POSIX
will standardise a new -mount option for find which is similar to
-xdev but differs in the way the mount point itself is handled. I
believe that the POSIX nftw() library function also gets a new option
FTW_XDEV,
Somewhat confusi
Hello,
I confirmed that
bison test 127. Tabulations and multibyte characters (for Maxwell's equations)
passed with the patch for m4/wcwidth.m4.
Regards,
--- Kiyoshi
- Original Message -
> From: Bruno Haible
> To: bug-gnulib@gnu.org
> Cc: Akim Demaille ; Kiyoshi KANAZAWA
>
> Date:
Hi Bruno,
On 05.05.19 02:24, Bruno Haible wrote:
> Tim Rühsen wrote:
>> Nothing documented found. After reading some code, it seems po/Makevars
>> is left alone when removing AM_GNU_GETTEXT_VERSION([0.17]) from
>> configure.ac.
>
> The Makefile.in.in from version 0.17 did not contain the support
Hi Akim,
> Is this what you have in mind?
OK, I now see where you are heading.
> +typedef struct argmatch_group
This type and the argmatch_usage function would go into argmatch.h or
in a new header file argmatch2.h or argmatch+.h, right?
> +static const char *const backup_docs[] =
> +{
> + N_
Hi,
> > 15 | e: {∇⃗×𝐸⃗ = -∂𝐵⃗/∂t}
> > - |^~
> > + |^
Indeed, mbswidth seems to have returned 3 more columns.
> The error (three more columns than expected) seems to indicate something
> related to the combining arrow.
No. The issue comes from th
Hi!
Bison uses mbswidth to track locations in grammar files. We recently
strengthened the test suite on this regard. It is reported to work
well on GNU/Linux and MacOS, but Kiyoshi reported a failure on Solaris
with UTF-8 (http://lists.gnu.org/archive/html/bug-bison/2019-04/msg00020.html):
> 12
10 matches
Mail list logo
