unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Service names on machines with bad service files
Date: Mon, 19 Sep 2011 15:07:28 -0400	[thread overview]
Message-ID: <87obyg9wr3.fsf@stupidchicken.com> (raw)
In-Reply-To: <m3vcsog9a7.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 19 Sep 2011 11:40:16 +0200")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> 2) Somehow determine that the OS doesn't know what "imaps" is, and use
>> "993" as a fallback.  I have no idea whether that's easy to do.
>
> This would be very easy to do.  It would mean making a new C-level
> function that basically just calls getservbyname and returns the port
> number.  So nnimap would the call `open-network-stream' with
> (or (service-port-number "imaps") 993).
>
> That sounds quite nice, doesn't it?

I'd rather use just 993.  Doing (or (service-port-number "imaps") 993)
doesn't really make sense.  OTOH, no one will ever change the service
names from their standard values, so the value will always be 993
anyway.



  parent reply	other threads:[~2011-09-19 19:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-19  9:30 Service names on machines with bad service files Lars Magne Ingebrigtsen
2011-09-19  9:40 ` Lars Magne Ingebrigtsen
2011-09-19 10:07   ` Julien Danjou
2011-09-19 19:07   ` Chong Yidong [this message]
2011-09-19 20:25     ` chad
2011-09-19 19:32 ` Andy Wingo
2011-09-25 11:40   ` Ted Zlatanov
2011-09-25 11:38 ` Ted Zlatanov
2011-09-26 17:01   ` Lars Magne Ingebrigtsen
2011-09-26 19:27     ` Ted Zlatanov
2011-09-26 19:33       ` Lars Magne Ingebrigtsen
2011-09-26 19:49         ` 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=87obyg9wr3.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).