unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Allow specifying services as symbols?
Date: Wed, 20 Oct 2010 11:21:06 -0500	[thread overview]
Message-ID: <87mxq8x2bx.fsf@lifelogs.com> (raw)
In-Reply-To: jwvd3r4ho8m.fsf-monnier+emacs@gnu.org

On Wed, 20 Oct 2010 11:36:00 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote: 

>> 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

SM> We're talking about an argument to a function, so it's not directly
SM> related to customization.  IOW if there's a problem with customization,
SM> it can be fixed elsewhere.

OK, let's forget about the patch.  There's too many useful cases where a
symbol could be passed to `make-network-process' as the service name and
trigger special behavior, plus there's no real need for changing the
current behavior.

Ted




  parent reply	other threads:[~2010-10-20 16:21 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
2010-10-20 16:10         ` Chong Yidong
2010-10-20 16:21         ` Ted Zlatanov [this message]
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

  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=87mxq8x2bx.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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 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).