From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Cc: guy@wyrdrune.com, "Kim F. Storm" <storm@cua.dk>,
Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Some findings and suggestion about Emacs on w32
Date: Tue, 26 Oct 2004 19:58:25 +0200 [thread overview]
Message-ID: <021501c4bb85$6d2f08e0$0200a8c0@sedrcw11488> (raw)
In-Reply-To: 1308.212.114.229.79.1098813296.squirrel@wwws.franken.de
----- Original Message -----
From: "Stephan Stahl" <stahl@eos.franken.de>
: I guess something like
: emacsclient -a emacs --eval (start-server)
: would meet Lennarts needs? But is there a reason that (start-server) is
not
: always called when emacs is started?
Maybe there are situations when you do not want the server to start. My
point is really that if you start Emacs with emacsclient then you probably
expect emacsserver to be started automatically.
If there are situations where you want to start Emacs without the server
then it would be much simpler if the server was not started by the init
files.
- Lennart
next prev parent reply other threads:[~2004-10-26 17:58 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 [this message]
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
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='021501c4bb85$6d2f08e0$0200a8c0@sedrcw11488' \
--to=lennart.borgman.073@student.lu.se \
--cc=emacs-devel@gnu.org \
--cc=guy@wyrdrune.com \
--cc=storm@cua.dk \
/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).