From: "Drew Adams" <drew.adams@oracle.com>
To: <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: RE: last-command-other-than-handle-switch-frame?
Date: Sun, 6 Jan 2008 11:41:28 -0800 [thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACIEHCCGAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1JBZvj-0001lk-CX@fencepost.gnu.org>
> I use non-nil pop-up-frames, so lots of `handle-switch-frame'
> commands get executed behind the scene. Why that is needed I've
> never quite understood - why should a focus event be treated as
> a "command"?
>
> The reason to make it generate an event is to make the command loop
> check for the new frame's buffer's keymaps.
>
> What does "treated as a command" mean?
Set `last-command' to it.
Again, if that is unavoidable, then how about also having a
`last-user-command' variable, which gets only user commands, not
pseudo-commands such as `handle-switch-frame'.
> For some time now, I've been coding ugly hacks like this:
>
> (if (memq last-command '(foo handle-switch-frame))...
>
> Does "treated as a command" mean that it goes into last-command?
Yes. That is what the annoyance is.
> I don't see any specific reason for doing so.
> Maybe we should change that.
That would be great.
> We cannot handle them thru special-event-map because they they would
> not cause the command loop to recheck the keymaps. But we could give
> it a definition that sets this-command to last-command, or something
> else with similar effect.
I would appreciate such a fix.
next prev parent reply other threads:[~2008-01-06 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 23:24 last-command-other-than-handle-switch-frame? Drew Adams
2008-01-06 18:09 ` last-command-other-than-handle-switch-frame? Richard Stallman
2008-01-06 19:41 ` Drew Adams [this message]
2008-01-07 11:31 ` last-command-other-than-handle-switch-frame? Richard Stallman
2008-01-14 19:13 ` last-command-other-than-handle-switch-frame? 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BNELLINCGFJLDJIKDGACIEHCCGAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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.