From: Noam Postavsky <npostavs@users.sourceforge.net>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 30207@debbugs.gnu.org
Subject: bug#30207: 27.0.50; [PATCH] other-window-for-scrolling returns window on daemon frame
Date: Mon, 22 Jan 2018 19:29:12 -0500 [thread overview]
Message-ID: <87h8rdo1t3.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87h8rdfnew.fsf@tcd.ie> (Basil L. Contovounesios's message of "Tue, 23 Jan 2018 00:07:19 +0000")
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
> I can't imagine a scenario where I would want to scroll a frame on a
> different terminal, so I personally prefer the bug#56160-style
> restriction to the current terminal for both its semantic and syntactic
> simplicity.
I believe some people use Emacs in a single-window-per-frame style and
manage the frames via the window manager, so scrolling in other
terminals sounds useful for that kind of scenario.
> OTOH, the other two approaches preserve established behaviour and also
> have the following merits:
>
> 1. Ignoring the daemon frame acts as a reminder to review the daemon
> frame visibility issue discussed in bug#27210.
Thanks for reminding us about it. :)
I'm still of the opinion that the daemon frame should be marked
invisible (what with it being not visible and all).
next prev parent reply other threads:[~2018-01-23 0:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 15:57 bug#30207: 27.0.50; [PATCH] other-window-for-scrolling returns window on daemon frame Basil L. Contovounesios
2018-01-22 18:59 ` martin rudalics
2018-01-23 0:07 ` Basil L. Contovounesios
2018-01-23 0:29 ` Noam Postavsky [this message]
2018-01-23 1:06 ` Basil L. Contovounesios
2018-01-23 1:29 ` Noam Postavsky
2018-01-23 13:28 ` Basil L. Contovounesios
2018-05-02 18:57 ` Basil L. Contovounesios
2018-05-02 19:44 ` Eli Zaretskii
2018-05-03 13:03 ` Basil L. Contovounesios
2018-05-03 19:00 ` Eli Zaretskii
2018-05-03 22:44 ` Basil L. Contovounesios
2018-05-10 23:48 ` Noam Postavsky
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=87h8rdo1t3.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=30207@debbugs.gnu.org \
--cc=contovob@tcd.ie \
/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.