From: Jim Meyering <jim@meyering.net>
To: Akim Demaille <akim.demaille@gmail.com>
Cc: "bug-gnulib@gnu.org List" <bug-gnulib@gnu.org>
Subject: Re: argmatch.h: new "_" definition may conflict with that of callers
Date: Tue, 2 Jul 2019 21:54:26 -0700 [thread overview]
Message-ID: <CA+8g5KFDki1K3VinxE9yRp+QaoG0MRrRNzSLXaL2hJSiM8HV3g@mail.gmail.com> (raw)
In-Reply-To: <DDB1555F-0906-438C-AE2F-61229AF4796A@gmail.com>
On Tue, Jul 2, 2019 at 9:48 PM Akim Demaille <akim.demaille@gmail.com> wrote:
> Bummer :( Sorry about that. I installed the following commit.
...
> + argmatch: don't define _ in the header.
> + Reported by Jim Meyering.
> + * lib/argmatch.h (N_, _): Don't define.
> + Use gettext instead.
> + * lib/argmatch.h (_): Define.
> + * tests/test-argmatch.c (N_): Define.
Thank you for the speedy fix!
next prev parent reply other threads:[~2019-07-03 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 4:17 argmatch.h: new "_" definition may conflict with that of callers Jim Meyering
2019-07-03 4:48 ` Akim Demaille
2019-07-03 4:54 ` Jim Meyering [this message]
2019-07-03 22:33 ` Bruno Haible
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+8g5KFDki1K3VinxE9yRp+QaoG0MRrRNzSLXaL2hJSiM8HV3g@mail.gmail.com \
--to=jim@meyering.net \
--cc=akim.demaille@gmail.com \
--cc=bug-gnulib@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).