all messages for Emacs-related lists mirrored at yhetil.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: Sun, 8 Jan 2012 15:00:16 -0800	[thread overview]
Message-ID: <510B6963E364499BBAF14665874F1C83@us.oracle.com> (raw)
In-Reply-To: <E1Rk1Js-0004jZ-TC@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.
> 
> We are not bureaucrats, we are developing software to be useful for
> users and to give them freedom.  We follow certain practical practices
> because they are generally helpful, but they are not imposed by gods.

I doubt anyone disagrees with that.  Just how is it relevant here?

The idea is to help Emacs users, including those writing Lisp code, by giving
them a heads-up wrt Emacs Dev support/intentions.  That, I presume, is the idea
behind functions such as `make-obsolete(-variable)': to inform users about
things that are considered obsolete.

Your thinking for 30 years that something is obsolete, and keeping the thought
to yourself, does not help users know that Emacs Development considers it so.

Have you considered for the same 30 years, since introducing Texinfo, that the
section of the `Info' manual that tells users how to write Info nodes by hand is
also obsolete?  If so, would it be bureaucratic to update that manual to reflect
your judgment, assuming the Emacs maintainers felt the same?

One need not be a bureaucrat or believe in gods to think that such communication
can be helpful to users.  Should we stop publishing NEWS because we are not
bureaucrats?




  reply	other threads:[~2012-01-08 23:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-27 22:37 bug#10385: e binding in info-mode Karl Berry
2012-01-06  8:11 ` Glenn Morris
2012-01-06 15:54   ` 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
2012-01-08  8:21                             ` Eli Zaretskii
2012-01-08 22:34                             ` Richard Stallman
2012-01-08 23:00                               ` Drew Adams [this message]
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

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

  git send-email \
    --in-reply-to=510B6963E364499BBAF14665874F1C83@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 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.