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: Thu, 23 Jun 2011 12:15:09 +0200 [thread overview]
Message-ID: <87mxh8onv6.fsf@gmail.com> (raw)
In-Reply-To: <4E030C18.9070205@gmx.at> (martin rudalics's message of "Thu, 23 Jun 2011 11:49:12 +0200")
martin rudalics <rudalics@gmx.at> writes:
>>> 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?
>
> The user could have made the window dedicated in which case
> `same-window' won't work. You should use a fallback in that case.
Ok thanks, i will try to fix this.
> Anyway, testing things with anything.el revealed three bugs in my code
> so this was a very fruitful experience for me. Please try your original
> code with the latest sources and tell me whether it works.
I will.
Here another one:
Use C-t while in anything.
=> byte-code: Attempt to split minibuffer window
Here relevant code in anything.el:
#+BEGIN_SRC lisp
;; Original function that fail
(defun anything-toggle-resplit-window ()
"Toggle resplit anything window, vertically or horizontally."
(interactive)
(with-anything-window
(let ((before-height (window-height)))
(delete-window)
(set-window-buffer
(select-window (if (= (window-height) before-height)
(split-window-vertically)
(split-window-horizontally)))
anything-buffer))))
;; A quick fix that fix it (not fully tested, just write quickly now)
(defun anything-toggle-resplit-window ()
"Toggle resplit anything window, vertically or horizontally."
(interactive)
(let (before-height)
(with-anything-window
(setq before-height (window-height))
(delete-window))
(with-selected-window (get-buffer-window anything-current-buffer)
(set-window-buffer
(select-window (if (= (window-height) before-height)
(split-window-vertically)
(split-window-horizontally)))
anything-buffer))))
#+END_SRC
--
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2011-06-23 10:15 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
2011-06-23 9:49 ` martin rudalics
2011-06-23 10:15 ` Thierry Volpiatto [this message]
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=87mxh8onv6.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).