From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: "J. Pablo Fernández" <pupeno@pupeno.com>, 646@debbugs.gnu.org
Subject: bug#646: emacsclient with no args to behave like -a
Date: Fri, 27 Aug 2021 06:14:56 +0200 [thread overview]
Message-ID: <87k0k7plq7.fsf@gnus.org> (raw)
In-Reply-To: <e53aa277-919a-5779-4d29-9ee3ca497968@gmail.com> (Jim Porter's message of "Thu, 26 Aug 2021 21:00:12 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
> From my reading, this is the original reporter's preferred behavior:
>
> 1) If Emacs is not currently running
> a) `emacsclient file.txt' starts Emacs and opens file.txt
> b) `emacsclient' starts Emacs (as though running `emacs')
> 2) If Emacs is currently running
> a) `emacsclient file.txt' opens file.txt in the existing Emacs session
> b) `emacsclient' brings some frame in the existing Emacs session
> to the foreground
That's not my reading. The bug reporter said "It would be nice if
emacsclient, when called with no arguments, would just run the alternate
editor." I.e., emulate the "-a" parameter when called with no
parameters.
(He's also using Emacs as the alternate, but that's just a detail.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-27 4:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 10:10 bug#646: No arguments J. Pablo Fernández
2008-08-04 14:27 ` Lennart Borgman (gmail)
2008-08-05 5:31 ` J. Pablo" Fernández
2008-08-05 9:33 ` Lennart Borgman (gmail)
2021-08-27 3:31 ` bug#646: emacsclient with no args to behave like -a Lars Ingebrigtsen
2021-08-27 4:00 ` Jim Porter
2021-08-27 4:14 ` Lars Ingebrigtsen [this message]
2021-08-27 5:06 ` Jim Porter
2021-08-27 14:50 ` Lars Ingebrigtsen
2021-08-27 17:18 ` Jim Porter
2021-08-28 15:02 ` Lars Ingebrigtsen
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=87k0k7plq7.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=646@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=pupeno@pupeno.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.
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).