unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Guy Gascoigne-Piggford <guy@wyrdrune.com>,
	Lennart Borgman <lennart.borgman.073@student.lu.se>,
	Jason Rumney <jasonr@gnu.org>,
	rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Some findings and suggestion about Emacs on w32
Date: Mon, 25 Oct 2004 14:06:42 +0200	[thread overview]
Message-ID: <m3zn2batnx.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <m17jpfjaix.fsf-monnier+emacs@gnu.org> (Stefan's message of "Mon, 25 Oct 2004 07:39:39 -0400")

Stefan <monnier@iro.umontreal.ca> writes:

>> I don't think we need to do this for 21.4 -- as the fix is only used
>> on (mostly) single user windoze.
>
> I guess if it's only used on w32 and we only bind to 127.0.0.1, it'd
> be acceptable.  But note that using a well-known port is a problem (we'd
> need to get it registered, ...).  

You don't need to register the port -- there are numerous well-known
but unregistered ports used everywhere.  And this port is only going
to be used locally -- not critical at all.

If you need to make it configurable, use a emacs-server-port variable
in emacs, and an environment variable (or registry key) in the client.


>                                   Better to let the OS choose the port and
> then store it in a file that emacsclient can read.  At that point, adding
> a secret random key to it isn't that much extra work.

Don't you need to add support for that random key to the protocol ?


-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2004-10-25 12:06 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 22:24 Some findings and suggestion about Emacs on w32 Lennart Borgman
2004-10-22 23:47 ` Kim F. Storm
2004-10-23 13:01   ` Lennart Borgman
2004-10-24 22:23     ` Kim F. Storm
2004-10-24 22:44       ` Stefan
2004-10-24 22:58         ` Guy Gascoigne-Piggford
2004-10-24 23:36           ` Stefan
2004-10-24 23:44             ` Lennart Borgman
2004-10-24 22:57       ` Guy Gascoigne-Piggford
2004-10-25  7:13       ` David Kastrup
2004-10-25  8:13         ` Kim F. Storm
2004-10-25 16:50       ` Lennart Borgman
     [not found]         ` <m3sm 81q3ut.fsf@kfs-l.imdomain.dk>
2004-10-26  8:29         ` Kim F. Storm
2004-10-26 17:29           ` Lennart Borgman
2004-10-26 17:43             ` Jason Rumney
2004-10-26 17:54               ` Stephan Stahl
2004-10-26 17:58                 ` Lennart Borgman
2004-10-26 21:59                   ` Kim F. Storm
2004-10-26 23:03                     ` Lennart Borgman
2004-10-26 17:55               ` Lennart Borgman
2004-10-26 18:50             ` Guy Gascoigne - Piggford
2004-10-26 20:48               ` Lennart Borgman
2004-10-23 12:42 ` Benjamin Riefenstahl
2004-10-23 13:15   ` Lennart Borgman
2004-10-23 13:40     ` Benjamin Riefenstahl
2004-10-23 17:39   ` Jason Rumney
2004-10-24 18:39     ` Benjamin Riefenstahl
2004-10-24 20:02       ` Jason Rumney
2004-10-24 20:25         ` Lennart Borgman
2004-10-24 20:43           ` Jason Rumney
2004-10-24 22:01             ` Guy Gascoigne-Piggford
2004-10-23 13:54 ` Richard Stallman
2004-10-23 17:44   ` Jason Rumney
2004-10-23 18:58     ` Guy Gascoigne-Piggford
2004-10-24  1:17       ` Lennart Borgman
2004-10-24 12:14       ` Jason Rumney
2004-10-24 12:46         ` Kim F. Storm
2004-10-25  4:30           ` Dhruva Krishnamurthy
2004-10-25 20:28             ` Lennart Borgman
2004-10-24 22:06         ` Stefan
2004-10-25  8:42         ` Kim F. Storm
2004-10-25  9:00           ` Guy Gascoigne-Piggford
2004-10-25  9:29             ` Kim F. Storm
2004-10-25 10:42               ` Dhruva Krishnamurthy
2004-10-25 11:39               ` Stefan
2004-10-25 12:06                 ` Kim F. Storm [this message]
2004-10-25 12:25                   ` Stefan

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=m3zn2batnx.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=guy@wyrdrune.com \
    --cc=jasonr@gnu.org \
    --cc=lennart.borgman.073@student.lu.se \
    --cc=rms@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).