all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "James Muchow" <jim_muchow@dell.com>, "Francesco Potortì" <pot@gnu.org>
Cc: 22306@debbugs.gnu.org
Subject: bug#22306: 24.5; Unhide --no-line-directive Documentation
Date: Sat, 09 Jan 2016 21:51:18 +0200	[thread overview]
Message-ID: <83vb72mszt.fsf@gnu.org> (raw)
In-Reply-To: <4800524ec80e46f5845c868a713dbbc0@mspexmb1.Beer.Town> (message from James Muchow on Mon, 4 Jan 2016 19:41:28 +0000)

> 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?

Thanks.





  reply	other threads:[~2016-01-09 19:51 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 [this message]
2016-01-09 23:26   ` Francesco Potortì
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=83vb72mszt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22306@debbugs.gnu.org \
    --cc=jim_muchow@dell.com \
    --cc=pot@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.
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.