From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 1298@emacsbugs.donarmstrong.com
Subject: bug#1298: allow 'emacsclient -a "emacs --daemon && emacsclient -c"'
Date: Tue, 18 Nov 2008 16:34:38 -0500 [thread overview]
Message-ID: <jwvvdukiutn.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <200811181817.mAIIHhEf001001@mothra.ics.uci.edu> (Dan Nicolaescu's message of "Tue, 18 Nov 2008 10:17:43 -0800 (PST)")
>> >> It would be nice if some equivalent of:
>> >> 'emacsclient -a "emacs --daemon && emacsclient -c"
>> >> would work.
>> >> That would allow one to ALWAYS use emacsclient.
>>
>> > Here's a quick hack that allows:
>> > emacsclient -a "emacs --daemon && emacsclient -c" FILENAME
>> > to work. It is not complete yet, FILENAME does not get passed to the
>> > "&& emacsclient"
>>
>> Here's an alternative:
>>
>> [ "$(emacsclient -e "'up" 2>/dev/null)" = "up" ] || emacs --daemon
>> emacsclient -c FILENAME
> I've been using something similar for a long time (even before
> --daemon), but it seems that it's more elegant to use a single command
> that shell hackery...
I think both are hacks, where my hack has the advantage of requiring no
changes to the code. If you want to change the code, than I'd rather we
do it Right.
Stefan
next prev parent reply other threads:[~2008-11-18 21:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812112123.mBBLNGpI001493@mothra.ics.uci.edu>
2008-11-02 18:18 ` bug#1298: allow 'emacsclient -a "emacs --daemon && emacsclient -c"' Dan Nicolaescu
2008-11-18 8:22 ` Dan Nicolaescu
2008-11-18 16:36 ` Stefan Monnier
2008-11-18 18:17 ` Dan Nicolaescu
2008-11-18 21:34 ` Stefan Monnier [this message]
2008-11-18 22:19 ` Dan Nicolaescu
2008-11-18 23:01 ` Stefan Monnier
2008-11-18 23:27 ` Dan Nicolaescu
2008-11-19 2:21 ` Stefan Monnier
2008-12-08 7:54 ` Dan Nicolaescu
2008-12-08 16:44 ` Stefan Monnier
2008-12-08 17:09 ` Dan Nicolaescu
2008-12-08 20:07 ` Stefan Monnier
2008-12-08 20:20 ` Dan Nicolaescu
2008-12-08 21:48 ` Stefan Monnier
2008-12-09 18:58 ` Dan Nicolaescu
2008-12-09 19:30 ` Juanma Barranquero
2008-12-09 20:07 ` Stefan Monnier
2008-12-10 7:58 ` Dan Nicolaescu
2008-12-10 9:49 ` Juanma Barranquero
2008-12-10 15:03 ` Dan Nicolaescu
2008-12-10 15:10 ` Juanma Barranquero
2008-12-10 15:29 ` Dan Nicolaescu
2008-12-10 15:32 ` Juanma Barranquero
2008-12-10 15:43 ` Dan Nicolaescu
2008-12-10 15:55 ` Juanma Barranquero
2008-12-11 16:37 ` Stefan Monnier
2008-12-11 17:08 ` Dan Nicolaescu
2008-12-11 19:05 ` Juanma Barranquero
2008-12-11 19:06 ` Stefan Monnier
2008-12-11 19:08 ` Juanma Barranquero
2008-12-11 19:28 ` Dan Nicolaescu
2008-12-11 19:58 ` Juanma Barranquero
2008-12-11 20:39 ` Dan Nicolaescu
2008-12-11 20:48 ` Juanma Barranquero
2008-12-11 20:58 ` Stefan Monnier
2008-11-18 23:01 ` Andreas Schwab
2008-11-18 19:43 ` Eli Zaretskii
2008-12-11 21:25 ` bug#1298: marked as done (allow 'emacsclient -a "emacs --daemon && emacsclient -c"') Emacs bug Tracking System
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=jwvvdukiutn.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=1298@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
/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).