From: "Francesco Potortì" <pot@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: James Muchow <jim_muchow@dell.com>, 22306@debbugs.gnu.org
Subject: bug#22306: 24.5; Unhide --no-line-directive Documentation
Date: Sun, 10 Jan 2016 00:26:55 +0100 [thread overview]
Message-ID: <E1aI2uN-0003we-Cv@tucano.isti.cnr.it> (raw)
In-Reply-To: <83vb72mszt.fsf@gnu.org>
>> From: James Muchow <jim_muchow@dell.com>
>> Date: Mon, 4 Jan 2016 19:41:28 +0000
>>
>> In trying to create a TAGS file, etags would process the
>> #line directive in various source files and produce TAGS
>> files that were unusable because the "file name" included
>> would be unavailable causing the tags-search to exit before
>> having seen all files.
>>
>> I spent a lot of time coming up with a solution to avoid
>> any files that contained a line directive when the solution
>> I really needed was already present: --no-line-directive.
>> It is, however, undocumented and thus the only way to know
>> about it is to download the source. I downloaded the source
>> to try and find out what etags was doing wrong with #line
>> when I discovered this undocumented option.
>>
>> I see from the source that the --no-line-directive is hidden
>> by the PRINT_UNDOCUMENTED_OPTIONS_HELP; I think it would be
>> helpful for others to remove this restriction.
>
>Francesco,
>
>Are there any reasons to keep this option (and a few others) hidden
>from the user eyes?
For this specific otion, the logs say that I undocumented it in 2002.
As far as I can recall, this was because the option seemed too much
technical to me, that is of little use and difficult to explain. I
think I adopted the same criterion for undocumenting the other options.
next prev parent reply other threads:[~2016-01-09 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 19:41 bug#22306: 24.5; Unhide --no-line-directive Documentation James Muchow
2016-01-09 19:51 ` Eli Zaretskii
2016-01-09 23:26 ` Francesco Potortì [this message]
2016-01-11 16:11 ` James Muchow
2016-01-15 8:58 ` Eli Zaretskii
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=E1aI2uN-0003we-Cv@tucano.isti.cnr.it \
--to=pot@gnu.org \
--cc=22306@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jim_muchow@dell.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.