From: Richard Stallman <rms@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: andreas.roehler@easy-emacs.de, emacs-devel@gnu.org
Subject: Re: auto-insert help-buffer
Date: Thu, 08 Mar 2007 16:48:30 -0500 [thread overview]
Message-ID: <E1HPQTO-0003LT-0P@fencepost.gnu.org> (raw)
In-Reply-To: <87fy8fu2kv.fsf@stupidchicken.com> (message from Chong Yidong on Thu, 08 Mar 2007 11:23:12 -0500)
We need to look for the solution in terms of what the user wants
in the various cases.
One possibility is to remove the unwind protect; the other is to check
in the mouse-click functions whether the desired window is live or
not. Which solution is preferable?
Both of them will make users unhappy. The first would mean that
typing SPC no longer gets rid of the help window. Clearly bad. The
second will avoid the error in these mouse commands, but it won't make
the commands actually _work_. So the user will be disappointed.
If a user clicks on the help buffer, he wants to operate on it. So
_in that case_, that window should not vanish. It should stay around
to be operated on.
Here's a way to implement it:
If the event that was read is a mouse event, and the buffer it's on is
the help buffer, it should discard the unwind-protect without
restoring the old window config.
If the event is not a mouse event, it should do what it does now.
It's not perfectly simple, but it is not very complex either.
Can you implement that?
next prev parent reply other threads:[~2007-03-08 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45D967C4.5060104@easy-emacs.de>
2007-03-08 16:23 ` auto-insert help-buffer Chong Yidong
2007-03-08 21:48 ` Richard Stallman [this message]
2007-03-09 2:06 ` Chong Yidong
2007-03-09 21:27 ` Richard Stallman
2007-03-10 4:48 ` Chong Yidong
2007-03-11 4:23 ` Richard Stallman
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=E1HPQTO-0003LT-0P@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=andreas.roehler@easy-emacs.de \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@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.