all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Francesco Potortì" <pot@gnu.org>
Cc: jim_muchow@dell.com, 22306-done@debbugs.gnu.org
Subject: bug#22306: 24.5; Unhide --no-line-directive Documentation
Date: Fri, 15 Jan 2016 10:58:43 +0200	[thread overview]
Message-ID: <83si1zfccc.fsf@gnu.org> (raw)
In-Reply-To: <E1aI2uN-0003we-Cv@tucano.isti.cnr.it> (message from Francesco Potortì on Sun, 10 Jan 2016 00:26:55 +0100)

> Date: Sun, 10 Jan 2016 00:26:55 +0100
> From: Francesco Potortì <pot@gnu.org>
> Cc: 22306@debbugs.gnu.org, James Muchow <jim_muchow@dell.com>
> 
> >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.

My forensic investigation of the history indicates that it was
first introduced in 2002, and undocumented in 2007.

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

Well, it seems this option is useful when the original file is no
longer available, which is a legitimate, albeit rare, use case.  So I
un-hided it, and also documented it in etags.1 as the fire-escape in
these rare use cases.

I'm therefore marking this bug done.

Thanks.





      parent reply	other threads:[~2016-01-15  8:58 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ì
2016-01-11 16:11     ` James Muchow
2016-01-15  8:58     ` Eli Zaretskii [this message]

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=83si1zfccc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22306-done@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.