all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: rms@gnu.org
Cc: andreas.roehler@easy-emacs.de, emacs-devel@gnu.org
Subject: Re: auto-insert help-buffer
Date: Fri, 09 Mar 2007 23:48:09 -0500	[thread overview]
Message-ID: <87y7m51z7a.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1HPmcI-0000f0-Im@fencepost.gnu.org> (Richard Stallman's message of "Fri\, 09 Mar 2007 16\:27\:10 -0500")

Richard Stallman <rms@gnu.org> writes:

>     !       record_unwind_protect (read_char_help_form_unwind, Qnil);
>     !       help_form_saved_window_configs
>     ! 	= Fcons (Fcurrent_window_configuration (Qnil),
>     ! 		 help_form_saved_window_configs);
>
> I would call record_unwind_protect after pushing the new element.
>
>     I cancel the window config unwinding as long as the user clicks
>     anywhere using the mouse, not just the help window---it's too much
>     trouble trying to identify the help window.
>
> How about if you assume that the most recently displayed window
> is the help window?

It's not foolproof, since display-buffer can reuse an existing window,
or pop up a new frame, or (with the appropriate user customizations)
something else entirely.  I think it's reasonable to expect that if
the user clicks somewhere, he or she does not expect the window
configuration to abruptly change "under the mouse pointer".

  reply	other threads:[~2007-03-10  4: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
2007-03-09  2:06     ` Chong Yidong
2007-03-09 21:27       ` Richard Stallman
2007-03-10  4:48         ` Chong Yidong [this message]
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=87y7m51z7a.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=andreas.roehler@easy-emacs.de \
    --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.