unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Tue, 21 Jun 2011 19:23:01 +0200	[thread overview]
Message-ID: <87fwn3umiy.fsf@gmail.com> (raw)
In-Reply-To: <4E00C2D1.2080902@gmx.at> (martin rudalics's message of "Tue, 21 Jun 2011 18:12:01 +0200")

martin rudalics <rudalics@gmx.at> writes:

>> The relevant code is in anything.el starting at line 3123 at:
>> ;; (@* "Utility: Persistent Action")
>>
>> and more exactly in `anything-persistent-action-display-buffer'.
>
> I tried to look at anything but it is much too complicated for me.
It is less complicated than display-buffer-alist ;-)

> Besides, evaluating anything-config.el gives the bug
What is evaluating? C-M-x?
Please use load or require.

>  global-set-key: Key sequence <f5> a starts with non-prefix key <f5>

Please follow instruction i gave you in precedent mail, or 
_load_ FIRST anything.el and SECOND anything-config.el.

I have no error here with emacs -Q.

Here a minimal config for anything with emacs -Q:

(add-to-list 'load-path "~/elisp/anything") ; Change path to anything
(require 'anything-config)

> Anyway: In the buggy version what is the value of NOT-THIS-WINDOW in the
> call to `display-buffer' in
> `anything-persistent-action-display-buffer'?
I think it is not called in old code, at least here, maybe it is used in
other libraries.

> And what is the selected window at that time?
It is the window containing the anything-buffer.

You can check with this:
--8<---------------cut here---------------start------------->8---
(defun anything-select-persistent-action-window ()
  (select-window (get-buffer-window (anything-buffer-get)))
  (message "%S" (get-buffer-window (anything-buffer-get)))
  (select-window
   (setq minibuffer-scroll-window
     (anything-persistent-action-display-window)))
   (message "%S" (anything-persistent-action-display-window)))
--8<---------------cut here---------------end--------------->8---


+---------------------------+
|                           |
| anything-current-buffer   |
| (the window to display    |
|  persistent action result)| In this case the result of
+---------------------------+ describe-function.
|                           |
| anything-buffer           |
| (selected window)         |
|                           |
+---------------------------+
| minibuffer                |
+---------------------------+


> The minibuffer window?
no

NOTE:
In fixed version using only:

--8<---------------cut here---------------start------------->8---
(when (boundp 'display-buffer-alist)
  (setq not-this-window '(reuse-window same other nil)))
(display-buffer buf not-this-window)))
--8<---------------cut here---------------end--------------->8---

is enough. (no pop-up-window entry)


--
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997



  reply	other threads:[~2011-06-21 17: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 [this message]
2011-06-22 16:00                           ` martin rudalics
2011-06-22 16:23                             ` Thierry Volpiatto
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

  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=87fwn3umiy.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 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).