From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Allow specifying services as symbols?
Date: Wed, 20 Oct 2010 11:36:00 -0400 [thread overview]
Message-ID: <jwvd3r4ho8m.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m37hhdu4o6.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 20 Oct 2010 01:46:33 +0200")
>>> As more of a philosophical objection than anything, t is a symbol.
>> Hmm, good catch. So's nil.
> True. Perhaps this isn't a good idea after all. It's just come more
> than a few times over the years that people are using 'nntp instead of
> "nntp" and 'imap instead of "imap" and not understanding why they're
> getting errors.
Maybe signalling a clear error would be a better choice.
> The issue came up as a customization user-side problem and I suggested
> allowing symbols. Using symbols is consistent with many other Emacs
> facilities (too many to list) that use symbols to enumerate a small set
> of choices. It makes customization simpler and less error-prone for
> software that uses `make-network-process'. It doesn't really cost
We're talking about an argument to a function, so it's not directly
related to customization. IOW if there's a problem with customization,
it can be fixed elsewhere.
Stefan
next prev parent reply other threads:[~2010-10-20 15:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 18:07 Allow specifying services as symbols? Lars Magne Ingebrigtsen
2010-10-19 18:22 ` Eli Zaretskii
2010-10-19 19:09 ` Ted Zlatanov
2010-10-19 20:17 ` Chong Yidong
2010-10-19 21:25 ` Ted Zlatanov
2010-10-19 21:32 ` Davis Herring
2010-10-19 22:20 ` Chong Yidong
2010-10-19 23:46 ` Lars Magne Ingebrigtsen
2010-10-20 15:36 ` Stefan Monnier [this message]
2010-10-20 16:10 ` Chong Yidong
2010-10-20 16:21 ` Ted Zlatanov
2010-10-20 11:32 ` Ted Zlatanov
2010-10-20 11:52 ` Andreas Schwab
2010-10-20 12:29 ` Ted Zlatanov
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=jwvd3r4ho8m.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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.