From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rms@gnu.org, emacs-devel@gnu.org, ams@gnu.org,
Ryan Yeske <rcyeske@gmail.com>,
storm@cua.dk, henrik.enberg@telia.com, miles@gnu.org
Subject: Re: rcirc.el
Date: Fri, 14 Oct 2005 22:43:08 -0400 [thread overview]
Message-ID: <87k6gfv72y.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <fc339e4a0510141408x32498ff5n@mail.gmail.com> (Miles Bader's message of "Sat, 15 Oct 2005 06:08:54 +0900")
>> I think it's best if the packages keep their names when they get
>> integrated, unless the name poses a real problem
> I do think that users should be able to start an irc session with M-x
> irc. We can do that without renaming everything.
We can provide an `irc' alias without any problem, indeed. It doesn't have
much to do with renaming or not.
> I think it depends a lot on exactly what the name is, and the
> package's history.
Sure. Since IIUC there are other IRC clients for Emacs out there, it makes
sense to be careful. Maybe none of them already use the name `irc', but you
never know. Furthermore, even without a long history, it
introduces confusion.
> But for packages with no significant independent history, which
> perform a fairly generic function in "the obvious way", calling every
> function "joes-great-foo-mode-asdf" instead of just "foo-asdf" is
> simply noise.
We're talking "rcirc" vs "irc". We're not talking some insanely long names.
Stefan
next prev parent reply other threads:[~2005-10-15 2:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 5:33 rcirc.el Ryan Yeske
2005-10-10 6:43 ` rcirc.el Alfred M. Szmidt
2005-10-14 4:20 ` rcirc.el Ryan Yeske
2005-10-14 17:37 ` rcirc.el Richard M. Stallman
2005-10-14 19:33 ` rcirc.el Ryan Yeske
2005-10-14 20:22 ` rcirc.el Miles Bader
2005-10-15 8:22 ` rcirc.el David Kastrup
2005-10-14 20:34 ` rcirc.el Stefan Monnier
2005-10-14 20:54 ` rcirc.el Ryan Yeske
2005-10-14 21:08 ` rcirc.el Miles Bader
2005-10-15 2:43 ` Stefan Monnier [this message]
2005-10-16 14:40 ` rcirc.el Richard M. Stallman
2005-10-16 15:16 ` rcirc.el Nic Ferrier
2005-10-18 7:03 ` rcirc.el Ryan Yeske
2005-10-18 7:45 ` rcirc.el Romain Francoise
2005-10-18 8:21 ` rcirc.el David Kastrup
2005-10-19 3:13 ` rcirc.el Ryan Yeske
2005-10-19 7:30 ` rcirc.el David Kastrup
2005-10-19 20:17 ` rcirc.el Richard M. Stallman
2005-10-19 9:56 ` rcirc.el Andreas Schwab
2005-10-19 20:15 ` rcirc.el Richard M. Stallman
2005-10-19 2:43 ` rcirc.el Richard M. Stallman
2005-10-19 7:20 ` rcirc.el Ryan Yeske
2005-10-19 20:17 ` rcirc.el Richard M. Stallman
2005-10-19 21:56 ` rcirc.el Ryan Yeske
2005-10-20 17:02 ` rcirc.el Richard M. Stallman
2005-10-20 17:58 ` rcirc.el Romain Francoise
2005-10-20 18:07 ` rcirc.el Henrik Enberg
2005-10-20 18:28 ` rcirc.el Romain Francoise
2005-10-10 9:57 ` rcirc.el Kim F. Storm
2005-10-10 10:08 ` rcirc.el Ryan Yeske
2005-10-10 10:31 ` rcirc.el Kim F. Storm
2005-10-10 12:58 ` rcirc.el Henrik Enberg
2005-10-10 13:16 ` rcirc.el Henrik Enberg
2005-10-10 16:06 ` rcirc.el Johan Bockgård
2005-10-10 15:25 ` rcirc.el Stefan Monnier
2005-10-10 23:47 ` rcirc.el Richard M. Stallman
-- strict thread matches above, loose matches on Subject: below --
2005-07-11 16:11 rcirc.el Ryan Yeske
2005-07-11 17:18 ` rcirc.el David Kastrup
2005-07-12 3:20 ` rcirc.el Richard M. Stallman
2005-07-12 4:55 ` rcirc.el Ryan Yeske
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=87k6gfv72y.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=ams@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=henrik.enberg@telia.com \
--cc=miles@gnu.org \
--cc=rcyeske@gmail.com \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
/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).