unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Daniel Colascione <dancol@dancol.org>
Cc: 10428@debbugs.gnu.org
Subject: bug#10428: 24.0.92; Please remove unnecessary alias `which-func-mode`
Date: Wed, 4 Jan 2012 02:03:31 +0100	[thread overview]
Message-ID: <CAAeL0SQ2ZMb4QPguuz8ydCsRmKk4oSZYPKE5QPhw0fY4UPWj9w@mail.gmail.com> (raw)
In-Reply-To: <4F03965C.7090401@dancol.org>

On Wed, Jan 4, 2012 at 00:59, Daniel Colascione <dancol@dancol.org> wrote:

> I thought the point was to not break existing _code_.

That's an interactive command. How it is used in lisp code is somewhat
less relevant.

> Making people
> change what they physically type isn't only acceptable, but desired:
> this way, we raise awareness of the new name.

Sometimes two names are just alternatives. And which-func-mode is shorter.

> I thought so. Maybe we should have commandp return nil for obsolete
> symbols.

I think you're thinking of `command-and-not-obsolete-p'... Which is to
say, I don't think changing the semantics of commandp is a good idea.

> make-obsolete already sets the byte-obsolete-info symbol
> property, which we could inspect easily enough.

And which is already done by the code that needs the info, like
`describe-function-1', `semantic-emacs-lisp-obsoleted-doc' and
`mh-make-local-hook'.

    Juanma





  reply	other threads:[~2012-01-04  1:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 22:50 bug#10428: 24.0.92; Please remove unnecessary alias `which-func-mode` Drew Adams
2012-01-03 23:42 ` Juanma Barranquero
2012-01-03 23:48   ` Daniel Colascione
2012-01-03 23:53     ` Juanma Barranquero
2012-01-03 23:59       ` Daniel Colascione
2012-01-04  1:03         ` Juanma Barranquero [this message]
2012-01-04  1:27           ` Leo
2012-01-04  1:31             ` Juanma Barranquero
2012-01-04  1:59               ` Leo
2012-01-03 23:56   ` Lars Magne Ingebrigtsen
2012-01-04  0:57     ` Juanma Barranquero
2012-01-05  4:59     ` Stefan Monnier
2012-01-07  0:26       ` Juanma Barranquero

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=CAAeL0SQ2ZMb4QPguuz8ydCsRmKk4oSZYPKE5QPhw0fY4UPWj9w@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=10428@debbugs.gnu.org \
    --cc=dancol@dancol.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).