From: James Nguyen <jamesn@fastmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 27511@debbugs.gnu.org
Subject: bug#27511: 26.0.50; emacsclient requires file argument
Date: Wed, 28 Jun 2017 20:35:58 -0700 [thread overview]
Message-ID: <5F318FAC-AA27-4F51-BB51-D41AF464D5AB@fastmail.com> (raw)
In-Reply-To: <87injfmw8e.fsf@users.sourceforge.net>
Hmnn, yeah sorry for not expounding earlier.
That snip you sent doesn’t work the way I want. It just opens the Gui Emacs up without opening a new scratch buffer.
At this point, my takeaway is that we think this is 1. not a bug and 2. unlikely to have the default change (emacsclient behaving similarly in spirit to emacs)
I will just have to write a bash function that wraps emacsclient and check for the file arg (or lackof) myself.
Thanks Noam for the help.
> On Jun 28, 2017, at 6:13 PM, npostavs@users.sourceforge.net wrote:
>
> James Nguyen <jamesn@fastmail.com> writes:
>
>> Those work for me but -c creates a new gui frame and -t opens in terminal.
>
> Oh, all the responses I saw in the reddit thread you linked were using
> -c or -t, so I thought that's what you wanted.
>
>> Usually I have a gui client up already and $ emacsclient $FILE is the
>> only choice that opens it in that current frame.
>
> But it sounds like you're actually after something like
>
> emacsclient --eval '(select-frame-set-input-focus (car (frame-list)))'
next prev parent reply other threads:[~2017-06-29 3:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 2:03 bug#27511: 26.0.50; emacsclient requires file argument James Nguyen
2017-06-28 14:45 ` Noam Postavsky
2017-06-28 15:00 ` James Nguyen
2017-06-28 17:03 ` Ken Brown
2017-06-28 17:22 ` James Nguyen
2017-06-28 17:35 ` Noam Postavsky
2017-06-28 23:49 ` James Nguyen
2017-06-29 1:13 ` npostavs
2017-06-29 3:35 ` James Nguyen [this message]
2017-06-29 12:32 ` npostavs
2017-06-29 14:11 ` Ken Brown
2017-06-29 16:48 ` James Nguyen
2017-06-29 18:11 ` Ken Brown
2017-06-30 1:06 ` James Nguyen
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=5F318FAC-AA27-4F51-BB51-D41AF464D5AB@fastmail.com \
--to=jamesn@fastmail.com \
--cc=27511@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.