unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: kgold@watson.ibm.com (kgold)
Subject: Re: automatic selection of emacsclient/emacs?
Date: 13 Jun 2005 18:27:52 GMT	[thread overview]
Message-ID: <42add028_1@news1.prserv.net> (raw)
In-Reply-To: vFXqe.56999$gc6.28085@okepread04

Dan Elliott <dan-underscore-elliott-at-cox-dot-net@spamispathetic.org> writes:
> Hattuari wrote:
> > Is there a clean way to get Emacs to start as a client when there is an
> > available server?  I find it moderately annoying to have to look around to
> > see if there is already an instance of Emacs started in order to determine
> > if I should enter `emacs' or `emacsclient'. I much prefer running
> > emacsclient when I already have one instance of Emacs running.  One option
> > is to try and sniff for emacs with ps and filter out the current processes
> > such as grep emacs, and (assuming the script I'm running is also called
> > emacs) the launch script.  It would seem more correct to directly check to
> > see if the service is available.  Is there such a capability? 
> 
> Will I get flammed if I ask what the benefit of running emacs as a 
> client (opposed to the "usual" way) would be?  Could this be an 
> alternative to using TRAMP?

To Dan:

As your .emacs gets bigger, the emacs startup time can become several
seconds.  With client/server, you just start emacs as a server once
per login, and the new emacs clients attach very quickly.

To Hattuari:

I use gnuserv/gnuclient, but this might help.  

I use the command 'emacs' once to start the server at login.  From
then on, I alias 'e' to gnuclient to start clients.  Since I always
start the emacs server at login to read mail, my 'e' command never has
to check if the server is running.

-- 
Ken Goldman   kgold@watson.ibm.com   914-784-7646

  parent reply	other threads:[~2005-06-13 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08  2:32 automatic selection of emacsclient/emacs? Hattuari
     [not found] ` <2cydneqEPbdzxTvfRVn-uw-zY4eFNvK5D9If6P1QZMOBw@public.gmane.org>
2005-06-08  7:56   ` Jochen Küpper
2005-06-08  8:00 ` Thorsten Bonow
2005-06-08  9:17 ` David Kastrup
2005-06-12 14:29 ` Dan Elliott
2005-06-12 18:19   ` Floyd L. Davidson
2005-06-13 15:29   ` Drew Adams
2005-06-13 18:27   ` kgold [this message]
2005-06-12 20:28 ` Benjamin Rutt

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=42add028_1@news1.prserv.net \
    --to=kgold@watson.ibm.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).