From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 25978@debbugs.gnu.org
Subject: bug#25978: 25.1; Message from `text-scale-adjust' is shown in other frames too
Date: Sun, 5 Mar 2017 08:56:41 -0800 (PST) [thread overview]
Message-ID: <7850719f-e07b-4aef-821d-df289d2ff6ed@default> (raw)
In-Reply-To: <c07ec6f7-675b-4a92-8c74-c2fe9417335c@default>
> > Here I see it only in the frame where I invoked "C-x -".
>
> After you see it there, click the title bar of the other frame,
> to select it. The message is moved to that (selected) frame's
> echo area. But using +, 0, or - in that frame does not have
> the effect of the message. That frame shows a different buffer,
> so +, 0, or - there is governed by the keymap of that buffer's
> frame.
Not sure what should happen instead (i.e., the proper fix).
The simplest fix, and probably the least confusing for users,
would be to cancel the command as soon as another frame is
selected.
Alternatively, we might try to make it so that if/when you
select the original frame again the command resumes where
it left off, with the same message etc.
I think the latter, besides being more complicated to
implement, might confuse a user who did a bunch of other
stuff before coming back to the original frame (selecting
it again). IOW, it would probably be better for the
command not to be modal in that buffer (resuming when its
frame is reselected), but just to be canceled as soon as
you select another frame.
next prev parent reply other threads:[~2017-03-05 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<c07ec6f7-675b-4a92-8c74-c2fe9417335c@default>
[not found] ` <<838tojk77w.fsf@gnu.org>
2017-03-05 16:13 ` bug#25978: 25.1; Message from `text-scale-adjust' is shown in other frames too Drew Adams
2017-03-05 16:40 ` Eli Zaretskii
2017-03-05 16:56 ` Drew Adams [this message]
2017-03-06 16:28 ` Eli Zaretskii
2017-03-05 16:51 ` Drew Adams
[not found] <<<c07ec6f7-675b-4a92-8c74-c2fe9417335c@default>
[not found] ` <<<838tojk77w.fsf@gnu.org>
[not found] ` <<7850719f-e07b-4aef-821d-df289d2ff6ed@default>
[not found] ` <<83h936id2w.fsf@gnu.org>
2017-03-06 16:52 ` Drew Adams
2017-03-06 18:42 ` Eli Zaretskii
2020-08-20 16:31 ` Lars Ingebrigtsen
2020-08-20 16:43 ` Eli Zaretskii
2022-02-08 6:34 ` Lars Ingebrigtsen
[not found] <<<<c07ec6f7-675b-4a92-8c74-c2fe9417335c@default>
[not found] ` <<<<838tojk77w.fsf@gnu.org>
[not found] ` <<<7850719f-e07b-4aef-821d-df289d2ff6ed@default>
[not found] ` <<<83h936id2w.fsf@gnu.org>
[not found] ` <<b6ee4368-ccff-43bc-9709-29f7da6ebe3f@default>
[not found] ` <<83bmtei6wc.fsf@gnu.org>
2017-03-06 18:46 ` Drew Adams
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=7850719f-e07b-4aef-821d-df289d2ff6ed@default \
--to=drew.adams@oracle.com \
--cc=25978@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).