[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Calling emacsclient
From: |
Suvayu Ali |
Subject: |
Re: Calling emacsclient |
Date: |
Mon, 12 Nov 2012 15:15:21 +0100 |
User-agent: |
Mutt/1.5.21 (2011-07-01) |
On Mon, Nov 12, 2012 at 02:04:31PM +0100, Thorsten Jolitz wrote:
> William Gardella <gardellawg@gmail.com> writes:
>
> > One possibility would be to use the emacsclient -s option together with
> > a shell wildcard, e.g.:
> >
> > emacsclient -c -s /tmp/emacs1000/*
> >
> > works, whatever the name of the socket inside /tmp/emacs1000/ is. So
> > you could use that trick with the value of your `server-socket-dir'
> > variable.
>
> I have the same 'server-socket-dir', so hardcoding this works fine on my
> machine. But what if I need a generic version? Can I get the value of
> `server-socket-dir' and use it for the '-s' option in the same external
> call to emacsclient? Or would I need two consecutive calls to
> emacsclient, the first one reading the value of `server-socket-dir' via
> 'emacsclient -e "(...some lisp...)"', the second one using it for the
> '-s' option from a variable of the calling program?
I believe a more generic server-socket-dir is /tmp/emacs${UID}/.
--
Suvayu
Open source is the future. It sets us free.