From: Eli Zaretskii <eliz@gnu.org>
To: Eliza Velasquez <exv@google.com>
Cc: 25547@debbugs.gnu.org, alexhutcheson@google.com,
monnier@iro.umontreal.ca
Subject: bug#25547: 25.1.91; emacsclient -c creates frames on the wrong display
Date: Sat, 07 Nov 2020 10:04:09 +0200 [thread overview]
Message-ID: <83v9eh7fuu.fsf@gnu.org> (raw)
In-Reply-To: <CAK1djOpxhzWL=2krbvG=qofGxUV_4f-7qtx0GvGJNkd309SyyQ@mail.gmail.com> (message from Eliza Velasquez on Fri, 6 Nov 2020 11:14:42 -0800)
> From: Eliza Velasquez <exv@google.com>
> Date: Fri, 6 Nov 2020 11:14:42 -0800
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 25547@debbugs.gnu.org,
> Alex Hutcheson <alexhutcheson@google.com>
>
> To answer your second question first, if we try to use
> server-create-tty-frame, Emacs will try to run display the frame in
> the terminal of the calling client, which it can't do in the case of a
> dumb terminal. The next best thing would be to allocate a new frame on
> an existing frame's terminal, whether that is on the tty or window
> system. Currently a dumb terminal running `emacsclient -c` can only
> create new frames on the window system, and this patch should allow it
> to create new frames on an existing tty terminal as well (once it's
> working correctly). As the initial report suggests, most of the time a
> dumb terminal is running `emacsclient -c`, its because it was called
> as part of a script in an Emacs subprocess.
Thanks for the explanation.
> Also, I'll rename the function to something like
> (server-create-frame-on-selected-terminal) since I agree its purpose
> is not clear from the name.
How about server-create-dumb-terminal-frame instead, since that's
what it really is?
next prev parent reply other threads:[~2020-11-07 8:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 18:09 bug#25547: 25.1.91; emacsclient -c creates frames on the wrong display Alex Hutcheson
2020-11-02 22:37 ` Stefan Monnier
[not found] ` <CAK1djOorpaeoMU-gtd+hQnWWK8tOaER6OPYgukYrn=V1cDh+aQ@mail.gmail.com>
[not found] ` <jwvsg9rtghs.fsf-monnier+emacs@gnu.org>
2020-11-03 18:36 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-05 2:00 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-05 4:44 ` Stefan Monnier
2020-11-05 23:41 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-06 0:55 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-06 5:39 ` Eli Zaretskii
2020-11-06 19:14 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-06 22:07 ` Stefan Monnier
2020-11-07 8:04 ` Eli Zaretskii [this message]
2020-11-10 0:14 ` Eliza Velasquez via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-11 3:14 ` Stefan Monnier
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=83v9eh7fuu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25547@debbugs.gnu.org \
--cc=alexhutcheson@google.com \
--cc=exv@google.com \
--cc=monnier@iro.umontreal.ca \
/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.