From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 36894@debbugs.gnu.org
Subject: bug#36894: Restore frameset focus and selectedness
Date: Thu, 15 Aug 2019 22:37:59 +0300 [thread overview]
Message-ID: <83lfvup6co.fsf@gnu.org> (raw)
In-Reply-To: <871rxmnumm.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 15 Aug 2019 21:36:33 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, 36894@debbugs.gnu.org
> Date: Thu, 15 Aug 2019 21:36:33 +0300
>
> Then I don't understand the logic of make-frame-command:
>
> (defun make-frame-command ()
> (interactive)
> (if (display-graphic-p)
> (make-frame)
> (select-frame (make-frame))))
>
> On a graphic display it doesn't select the new frame explicitly,
> maybe on the assumption that all window managers should select it
> afterwards?
On a TTY, if you don't select the new frame, it is invisible. On a
GUI display, the new frame is visible, so there's no need to
explicitly select it, because no one said the user wants the new frame
become selected.
next prev parent reply other threads:[~2019-08-15 19:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 21:34 bug#36894: Stability issues in frameset sorting Juri Linkov
2019-08-05 21:17 ` Juri Linkov
2019-08-06 15:14 ` Eli Zaretskii
2019-08-06 22:09 ` Juri Linkov
2019-08-07 2:29 ` Eli Zaretskii
2019-08-09 18:09 ` Juri Linkov
2019-08-09 19:04 ` Eli Zaretskii
2019-08-11 20:51 ` bug#36894: Restore frameset focus and selectedness Juri Linkov
2019-08-12 15:00 ` Eli Zaretskii
2019-08-13 21:29 ` Juri Linkov
2019-08-14 8:58 ` martin rudalics
2019-08-14 14:25 ` Eli Zaretskii
2019-08-14 20:50 ` Juri Linkov
2019-08-15 8:12 ` martin rudalics
2019-08-15 18:36 ` Juri Linkov
2019-08-15 19:37 ` Eli Zaretskii [this message]
2019-08-16 7:29 ` martin rudalics
2019-08-17 7:19 ` Eli Zaretskii
2019-08-17 8:24 ` martin rudalics
2019-08-17 10:12 ` Eli Zaretskii
2019-08-17 22:40 ` Juri Linkov
2019-08-19 7:38 ` martin rudalics
2019-08-14 20:49 ` Juri Linkov
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=83lfvup6co.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36894@debbugs.gnu.org \
--cc=juri@linkov.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.