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: Service names on machines with bad service files
Date: Sun, 25 Sep 2011 06:38:01 -0500	[thread overview]
Message-ID: <8762kg97ja.fsf@lifelogs.com> (raw)
In-Reply-To: m339fshob5.fsf@stories.gnus.org

On Mon, 19 Sep 2011 11:30:22 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> A Windows user has a problem with opening a connection using port
LMI> "imaps", which doesn't exist in that user's service file (or wherever
LMI> Windows stashes these things).

LMI> So I'm wondering whether there's any nice way to determine that that's
LMI> the situation and work around it.
...
LMI> 2) Somehow determine that the OS doesn't know what "imaps" is, and use
LMI> "993" as a fallback.  I have no idea whether that's easy to do.

I think this is the best solution: map service names to ports in an
OS-specific way.

For W32, http://support.microsoft.com/kb/832017 could be used.  It gives
several standard port assignments in tables.  That whole article could
be transformed into a "services" file at compile time or provided
dynamically.

Ted




  parent reply	other threads:[~2011-09-25 11:38 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
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 [this message]
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=8762kg97ja.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).