From: Florian Weimer <fweimer@redhat.com>
To: Girish Joshi <girish946@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] argp: argp.doc prints incorrectly when it starts with "\v" [BZ #19038]
Date: Mon, 06 May 2019 12:37:00 -0000 [thread overview]
Message-ID: <871s1bep2u.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CALkY8p960_gyY_Q1C+FPKuRYYyBCyp7V=PZpu8XaNW5Mxkxdgg@mail.gmail.com> (Girish Joshi's message of "Mon, 6 May 2019 04:55:33 -0400")
* Girish Joshi:
> In argp-help.c `char *vt` is being initialized only once. It needs to
> be initialized for every child in the doc and it needs to be printed
> only in two cases.
> 1. There are no children and the doc does not starts with '\v'.
> 2. Argument `first_only` to the function `argp_doc` is false and the
> complete doc needs to be printed.
I assume this bug user-visible, so it should have a bug in Bugzilla
<https://sourceware.org/bugzilla/>. Would you please file one?
Could you write a test case for this? Or at least post how to reproduce
the issue in a minimal program?
Thanks,
Florian
next prev parent reply other threads:[~2019-05-06 12:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 8:55 Girish Joshi
2019-05-06 12:37 ` Florian Weimer [this message]
2019-05-06 13:38 ` Girish Joshi
2019-05-30 8:14 ` Girish Joshi
2019-05-30 12:52 ` Adhemerval Zanella
2019-07-05 9:02 ` Girish Joshi
2019-07-05 10:35 ` Girish Joshi
2019-07-25 15:33 ` Joseph Myers
2019-11-25 18:08 ` Girish Joshi
2019-11-30 14:47 ` Girish Joshi
2019-11-30 15:05 ` Carlos O'Donell
2020-01-07 17:55 ` Girish Joshi
2020-01-20 17:39 ` Girish Joshi
2020-01-24 2:59 ` Carlos O'Donell
2020-02-11 18:40 ` Girish Joshi
2020-02-20 7:09 ` Girish Joshi
2020-03-03 18:13 Girish Joshi
2020-03-19 19:38 ` Girish Joshi
2020-03-21 2:03 ` DJ Delorie
2020-03-25 17:55 ` Girish Joshi
2020-05-07 19:53 ` Girish Joshi
2020-05-23 10:10 ` Girish Joshi
2020-06-14 15:50 ` Girish Joshi
2020-06-15 8:56 ` Florian Weimer
2020-06-15 9:51 ` Girish Joshi
2020-06-15 14:38 ` Zack Weinberg
2021-02-18 21:13 ` Girish Joshi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871s1bep2u.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=girish946@gmail.com \
--cc=libc-alpha@sourceware.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).