From: Daiki Ueno <ueno@unixuser.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: 733@emacsbugs.donarmstrong.com
Subject: bug#733: 23.0.60; epa-list-keys buffer behaves strangely
Date: Tue, 26 Aug 2008 12:24:56 +0900 [thread overview]
Message-ID: <87vdxo7913.fsf@broken.deisui.org> (raw)
In-Reply-To: <17A7D165-525D-4B68-840F-5CF9654289FF@Freenet.DE> (Peter Dyballa's message of "Thu, 21 Aug 2008 23:10:48 +0200")
>>>>> In <17A7D165-525D-4B68-840F-5CF9654289FF@Freenet.DE>
>>>>> Peter Dyballa <Peter_Dyballa@Freenet.DE> wrote:
> Am 21.08.2008 um 09:18 schrieb Daiki Ueno:
> > How about the following?
> >
> > (eval-after-load "epa"
> > '(defun epa--key-widget-action (widget &optional event)
> > (save-selected-window
> > (epa--show-key (widget-get widget :value)))))
> >
> > (setq widget-button-click-moves-point t)
> Yes, this introduces a clear behaviour. Thank you! IMO it should
> become default behaviour.
I've just intalled the former. I leave the setting of
`widget-button-click-moves-point' up to users since other Elisp programs
do not bind this variable.
> There is another behaviour that should be changed. When I move the
> mouse cursor away from the previously selected key, or change to
> another buffer or another application, the green marker colour goes
> away, i.e., the selection seems to be lost. When I move the mouse
> cursor over other keys, the green colour follows the mouse cursor.
> IMO the previous selection should be kept (the *Key*<number> buffer
> does not change yet), and the mouse cursor should high-light in a
> different colour, maybe yellow, as with traffic lights, because the
> mouse cursor could select another key at any time.
Well, I think this behaviour not feasible for some reason. First, there
is no concept of "selected key" in epa-key-list-mode. If there are a
couple of key (say AAAAAA and BBBBBB), you select them consequently, and
you will see two buffers named "*Key*AAAAAA" and "*Key*BBBBBB".
Second, I have never heard of any way to catch the event which "changes
to another buffer" (perhaps impossible).
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2008-08-26 3:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 23:30 bug#733: 23.0.60; epa-list-keys buffer behaves strangely Peter Dyballa
2008-08-21 7:18 ` Daiki Ueno
2008-08-21 21:10 ` Peter Dyballa
2008-08-26 3:24 ` Daiki Ueno [this message]
2011-07-09 5:37 ` Glenn Morris
-- strict thread matches above, loose matches on Subject: below --
2008-08-18 20:08 Chong Yidong
2008-08-18 20:20 ` Peter Dyballa
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=87vdxo7913.fsf@broken.deisui.org \
--to=ueno@unixuser.org \
--cc=733@emacsbugs.donarmstrong.com \
--cc=Peter_Dyballa@Freenet.DE \
/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).