From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: pop-to-buffer and friends new behavior or bug?
Date: Wed, 22 Jun 2011 18:23:07 +0200 [thread overview]
Message-ID: <87mxh96djo.fsf@gmail.com> (raw)
In-Reply-To: <4E02119A.8040109@gmx.at> (martin rudalics's message of "Wed, 22 Jun 2011 18:00:26 +0200")
martin rudalics <rudalics@gmx.at> writes:
> OK. I managed to reproduce the behavior now. It's due to a silly bug
> in `display-buffer-pop-up-window'. I'll install a fix soon.
Nice thanks.
>> +---------------------------+
>> | |
>> | anything-current-buffer |
>> | (the window to display |
>> | persistent action result)| In this case the result of
>> +---------------------------+ describe-function.
>> | |
>> | anything-buffer |
>> | (selected window) |
>> | |
>> +---------------------------+
>> | minibuffer |
>> +---------------------------+
>
> I can't follow you here. When I invoke C-z the window showing the
> anything-current-buffer becomess the selected window. That seems
> intentional - because *Help* is by default shown in the selected window
> and `describe-function' shows the result in that buffer.
Yes it is intentional.
> If a user changes that setting, this mechanism won't work as intended.
Which different setting a user could use here for example?
pop-up-frames?
(i mean for displaying help buffer.)
> Or am I missing something?
No you're right here, maybe my explanation was bad.
--
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2011-06-22 16:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 18:02 pop-to-buffer and friends new behavior or bug? Thierry Volpiatto
2011-06-16 20:16 ` Thierry Volpiatto
2011-06-16 20:35 ` martin rudalics
2011-06-16 22:00 ` Thierry Volpiatto
2011-06-17 15:46 ` martin rudalics
2011-06-17 16:01 ` Thierry Volpiatto
2011-06-18 16:10 ` martin rudalics
2011-06-18 17:19 ` Thierry Volpiatto
2011-06-18 19:53 ` Thierry Volpiatto
2011-06-19 13:26 ` martin rudalics
2011-06-19 18:49 ` Thierry Volpiatto
2011-06-20 8:29 ` Thierry Volpiatto
2011-06-20 9:24 ` martin rudalics
2011-06-20 9:59 ` Thierry Volpiatto
2011-06-21 13:25 ` Thierry Volpiatto
2011-06-21 14:41 ` martin rudalics
2011-06-21 15:11 ` Thierry Volpiatto
2011-06-21 16:12 ` martin rudalics
2011-06-21 17:23 ` Thierry Volpiatto
2011-06-22 16:00 ` martin rudalics
2011-06-22 16:23 ` Thierry Volpiatto [this message]
2011-06-23 9:49 ` martin rudalics
2011-06-23 10:15 ` Thierry Volpiatto
2011-06-23 11:07 ` martin rudalics
2011-06-23 15:56 ` Thierry Volpiatto
2011-06-23 16:07 ` martin rudalics
2011-06-23 17:22 ` Thierry Volpiatto
2011-06-23 18:51 ` Thierry Volpiatto
2011-06-24 7:01 ` martin rudalics
2011-06-24 7:10 ` Thierry Volpiatto
2011-06-16 21:10 ` David Koppelman
2011-06-17 15:46 ` martin rudalics
2011-06-19 13:27 ` martin rudalics
2011-06-20 19:17 ` David Koppelman
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=87mxh96djo.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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.