unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <rms@gnu.org>
Cc: juri@jurta.org, eliz@gnu.org, emacs-devel@gnu.org
Subject: RE: bug#10385: e binding in info-mode
Date: Sat, 7 Jan 2012 23:03:15 -0800	[thread overview]
Message-ID: <3D4EE65ECFA64F7C8CDEFF55A750E37C@us.oracle.com> (raw)
In-Reply-To: <E1RjlSm-0005lh-3g@fencepost.gnu.org>

> I have considered Info-edit obsolete ever since we had Texinfo.

If you don't tell the users that something is deprecated/obsolete, then such
interior consideration doesn't mean much.

It makes sense to let users know what to expect in terms of support etc.  And
that is pretty typical.

> Info has existed since 1976 or so, in the original Emacs.  At that
> time, Info files were written by hand, and everyone could edit system
> files on ITS.  Thus, Info-edit was useful there.
> 
> When I implemented info in GNU Emacs, I wrote Info-edit there too.
> Then I implemented Texinfo to format the Emacs manual.  This made
> Info-edit useless when Texinfo is in use -- which ought to be always.

Dunno why it "ought" to be.  But I won't argue the point.  (But see my other
reply.)

> Meanwhile, ordinary users can't edit the installed Info files anyway.

Why not?  What prevents them?

> So Info-edit is basically useless.

So you could have deprecated it, uh, let's see, about 30 years ago, and you've
known that for that time.  Apparently there has been no hurry. ;-)

Might as well deprecate it now and desupport it in Emacs 24.2 (or 29.3), I
guess.




  reply	other threads:[~2012-01-08  7:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201112272237.pBRMbo8C022896@freefriends.org>
     [not found] ` <62fwftxnbz.fsf@fencepost.gnu.org>
2012-01-06 15:54   ` bug#10385: e binding in info-mode Drew Adams
2012-01-06 16:07     ` Eli Zaretskii
2012-01-07  0:12       ` Richard Stallman
2012-01-07 20:27         ` Juri Linkov
2012-01-07 21:26           ` Drew Adams
2012-01-07 21:46             ` Juri Linkov
2012-01-07 22:15               ` Drew Adams
2012-01-07 23:10                 ` Juri Linkov
2012-01-07 23:27                   ` Drew Adams
2012-01-07 23:47                     ` Juri Linkov
2012-01-08  1:08                       ` Drew Adams
2012-01-08  5:38                         ` Richard Stallman
2012-01-08  7:03                           ` Drew Adams [this message]
2012-01-08  8:21                             ` Eli Zaretskii
2012-01-08 22:34                             ` Richard Stallman
2012-01-08 23:00                               ` Drew Adams
2012-01-09 15:55                                 ` Richard Stallman
2012-01-08  5:38             ` Richard Stallman
2012-01-08  7:02               ` Drew Adams
2012-01-08  5:37           ` Richard Stallman
2012-01-08 14:13           ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D4EE65ECFA64F7C8CDEFF55A750E37C@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=rms@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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