From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Andreas Schwab <schwab@linux-m68k.org>,
Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] manual: Clarify that abbreviations of long options are allowed
Date: Wed, 4 May 2022 08:26:44 +0530 [thread overview]
Message-ID: <a8b872a2-b791-4359-47b4-7e7832fbc884@sourceware.org> (raw)
In-Reply-To: <87ilqnf4pr.fsf@igel.home>
On 03/05/2022 13:06, Andreas Schwab wrote:
> On Mai 03 2022, Siddhesh Poyarekar via Libc-alpha wrote:
>
>> diff --git a/manual/getopt.texi b/manual/getopt.texi
>> index 5485fc4694..e58283ab88 100644
>> --- a/manual/getopt.texi
>> +++ b/manual/getopt.texi
>> @@ -250,7 +250,8 @@ option, and stores the option's argument (if it has one) in @code{optarg}.
>>
>> When @code{getopt_long} encounters a long option, it takes actions based
>> on the @code{flag} and @code{val} fields of the definition of that
>> -option.
>> +option. The option name may be abbreviated as long as the abbreviation is
>> +unique or is an exact match for some defined option.
>
> If it's an exact match, it isn't an abbreviation?
>
So just the following?
The option name may be abbreviated as long as the abbreviation is unique.
Thanks,
Siddhesh
next prev parent reply other threads:[~2022-05-04 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 4:57 Siddhesh Poyarekar
2022-05-03 5:13 ` Florian Weimer
2022-05-03 7:36 ` Andreas Schwab
2022-05-04 2:56 ` Siddhesh Poyarekar [this message]
2022-05-04 7:38 ` Andreas Schwab
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=a8b872a2-b791-4359-47b4-7e7832fbc884@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).