From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Calling emacsclient
Date: Mon, 12 Nov 2012 15:15:21 +0100 [thread overview]
Message-ID: <20121112141521.GC14125@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87haovq8f4.fsf@googlemail.com>
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.
next prev parent reply other threads:[~2012-11-12 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12766.1352681489.855.help-gnu-emacs@gnu.org>
2012-11-12 5:03 ` Calling emacsclient William Gardella
2012-11-12 13:04 ` Thorsten Jolitz
2012-11-12 14:15 ` Suvayu Ali [this message]
2012-11-12 14:58 ` Thorsten Jolitz
2012-11-14 13:53 ` Thorsten Jolitz
[not found] ` <mailman.12968.1352901198.855.help-gnu-emacs@gnu.org>
2012-11-14 17:10 ` William Gardella
2012-11-14 20:08 ` Thorsten Jolitz
2012-11-14 17:22 ` William Gardella
2012-11-14 17:23 ` William Gardella
2012-11-14 20:01 ` Thorsten Jolitz
2012-11-12 0:51 Thorsten Jolitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121112141521.GC14125@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.