From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: James Muchow Newsgroups: gmane.emacs.bugs Subject: bug#22306: 24.5; Unhide --no-line-directive Documentation Date: Mon, 11 Jan 2016 16:11:45 +0000 Message-ID: <8543a3ac28a841169e403b2bd50610c7@mspexmb1.Beer.Town> References: <4800524ec80e46f5845c868a713dbbc0@mspexmb1.Beer.Town> <83vb72mszt.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1452528761 16636 80.91.229.3 (11 Jan 2016 16:12:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 11 Jan 2016 16:12:41 +0000 (UTC) Cc: "22306@debbugs.gnu.org" <22306@debbugs.gnu.org> To: Francesco =?UTF-8?Q?Potort=C3=AC?= , Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Jan 11 17:12:34 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aIf53-0004rG-1f for geb-bug-gnu-emacs@m.gmane.org; Mon, 11 Jan 2016 17:12:29 +0100 Original-Received: from localhost ([::1]:55545 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aIf52-0007fJ-BU for geb-bug-gnu-emacs@m.gmane.org; Mon, 11 Jan 2016 11:12:28 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60838) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aIf4g-00073P-HJ for bug-gnu-emacs@gnu.org; Mon, 11 Jan 2016 11:12:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aIf4c-0000QB-FL for bug-gnu-emacs@gnu.org; Mon, 11 Jan 2016 11:12:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:58403) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aIf4c-0000Q7-6O for bug-gnu-emacs@gnu.org; Mon, 11 Jan 2016 11:12:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aIf4c-0003NN-3A for bug-gnu-emacs@gnu.org; Mon, 11 Jan 2016 11:12:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: James Muchow Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 11 Jan 2016 16:12:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22306 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 22306-submit@debbugs.gnu.org id=B22306.145252871512950 (code B ref 22306); Mon, 11 Jan 2016 16:12:02 +0000 Original-Received: (at 22306) by debbugs.gnu.org; 11 Jan 2016 16:11:55 +0000 Original-Received: from localhost ([127.0.0.1]:46620 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aIf4U-0003Mn-S5 for submit@debbugs.gnu.org; Mon, 11 Jan 2016 11:11:55 -0500 Original-Received: from aussmtpmrkpc120.us.dell.com ([143.166.82.159]:31086) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aIf4T-0003Ma-93 for 22306@debbugs.gnu.org; Mon, 11 Jan 2016 11:11:53 -0500 X-Loopcount0: from 76.164.8.179 X-IronPort-AV: E=Sophos;i="5.20,553,1444712400"; d="scan'208";a="346897228" Thread-Topic: bug#22306: 24.5; Unhide --no-line-directive Documentation Thread-Index: AdFHJ+ZmoutXFiH+S2qwAs25Jng9dQD70arOABQV54AASCP6EA== In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.31.101.17] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:111497 Archived-At: > From: Francesco Potort=EC [mailto:pot@gnu.org]=20 > Sent: Saturday, January 09, 2016 5:27 PM >>> From: James Muchow >>> Date: Mon, 4 Jan 2016 19:41:28 +0000 >>>=20 >>> In trying to create a TAGS file, etags would process the >>> #line directive in various source files and produce TAGS=20 >>> files that were unusable because the "file name" included >>> would be unavailable causing the tags-search to exit before >>> having seen all files. >>>=20 >>> 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. >>>=20 >>> 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, >>=20 >> 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. First of all thanks for cleaning up my request and getting rid of all the extraneous verbiage. I've never filed a bug report before, so I didn't quite know what to expect. Anyway... I am aware that the documentation hiding was done years ago. As to whether it is too technical or not; the fact is that in our environment, the TAGS files I produced are useless (30M of=20 useless) and that was quickly diagnosed to those files that use=20 the #line directive. Resolving this issue involved, as I wrote, a lot of time when the solution was already present the whole time. A solution of which I was unaware because it was deemed too technical. I now know of this option, so I could take the "I don't care, I got mine" approach, but I thought that such a trivial fix might be turn out to be helpful to someone else. But YMMV, I'll leave the eventual resolution in your hands.