From: noreply@yeahoo.com
Subject: Re: Check for other running emacs sessions?
Date: Thu, 06 Apr 2006 13:23:53 -0700 [thread overview]
Message-ID: <m2sloq312e.fsf@d-128-95-226-228.dhcp4.washington.edu> (raw)
In-Reply-To: mailman.122.1144332075.9609.help-gnu-emacs@gnu.org
Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
> kgold wrote:
>> A better solution is to run only one emacs server and connect
>> multiple clients to it. That is, start gnuserv as part of your
>> login script. Use gnuclient to edit files.
>>
>> The main advantage is that the client starts much faster than the server.
It is only a good solution to run one emacs and multiple clients if
you don't ever run anything that ties emacs up. If emacs is doing
something or waiting for a process to complete, you often cannot work
on any other buffers under that instance of emacs. I don't like not
being able to update my calendar because gnus is checking my mail, for
example.
> Another advantage is that you can not by mistake open a file twice.
This is a disadvantage, but a minor one to me. I segregate tasks
under different instances of emacs, so it doesn't happen much.
Brian
next prev parent reply other threads:[~2006-04-06 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 23:11 Check for other running emacs sessions? noreply
2006-04-05 23:39 ` Pascal Bourguignon
2006-04-06 12:49 ` kgold
2006-04-06 14:00 ` Lennart Borgman
2006-04-06 16:32 ` Reiner Steib
[not found] ` <mailman.122.1144332075.9609.help-gnu-emacs@gnu.org>
2006-04-06 20:23 ` noreply [this message]
2006-04-06 21:24 ` Lennart Borgman
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=m2sloq312e.fsf@d-128-95-226-228.dhcp4.washington.edu \
--to=noreply@yeahoo.com \
/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.
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).