From: "Drew Adams" <drew.adams@oracle.com>
To: "'Štepán Nemec'" <stepnem@gmail.com>
Cc: 'Andreas Schwab' <schwab@linux-m68k.org>, 9274@debbugs.gnu.org
Subject: bug#9274: 24.0.50; doc string of `normal-top-level-add-subdirs-to-load-path'
Date: Wed, 10 Aug 2011 14:37:54 -0700 [thread overview]
Message-ID: <EE05C4D96F274561B30ED21B4361B579@us.oracle.com> (raw)
In-Reply-To: <87vcu59jsa.fsf@gmail.com>
> > Anyway, this discussion is peripheral to this bug. The
> > name is monstrous, but it is unlikely that it will ever be changed...
>
> Why is that unlikely?
I can't really speak to whether it is unlikely or why it would be - I misspoke.
I should have said that my _guess_ is that it is unlikely.
And that guess is not based on any good reason I know of why it should not be
changed. On the contrary...
> What's wrong with adding a more sensible alias,
> optionally declaring the old name obsolete?
> Standard procedure, it's done every now and then.
Sounds good to me. And yes, it is.
> The question is whether the maintainers acknowledge the problem
> or not -- I for one don't use the function even though I've known
> about it for some time, but I know people who do use it, and the
> docstring suggests general usefulness. One more argument for
> "it's a lousy name".
Same here - on all accounts: Yes, that is the question. I haven't used it. But I
see it called out in recommendations here and there (e.g. the wiki) to users.
next prev parent reply other threads:[~2011-08-10 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 22:25 bug#9274: 24.0.50; doc string of `normal-top-level-add-subdirs-to-load-path' Drew Adams
2011-08-09 23:11 ` Štěpán Němec
2011-08-10 16:02 ` Andreas Schwab
2011-08-10 16:34 ` Drew Adams
2011-08-10 18:57 ` Štěpán Němec
2011-08-10 21:37 ` Drew Adams [this message]
2011-08-20 19:30 ` Chong Yidong
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=EE05C4D96F274561B30ED21B4361B579@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9274@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=stepnem@gmail.com \
/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).