From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: 3419@debbugs.gnu.org
Subject: bug#3419: 23.0.94; calc, calendar and temp-buffer-resize-mode
Date: Fri, 04 Nov 2011 10:39:05 +0100 [thread overview]
Message-ID: <4EB3B2B9.9010808@gmx.at> (raw)
In-Reply-To: <8762j1htx9.fsf@mail.jurta.org>
> The goal can be achieved for calendar with the patch I sent in another
> message. For ibuffer and buff-menu I see no problem.
You mean doing the same as in calendar? Things like
(lambda (buf)
(split-window nil height (eq type 'horizontally))
(other-window 1)
(switch-to-buffer buf)))
look suspicious because `switch-to-buffer' without FORCE-SAME-WINDOW set
can now make the behavior differently wrt Emacs 23.
> For ispell
> I guess you mean your test case with `display-buffer-pop-up-frame'?
No. I mean the same as above. More precisely
(let ((choices-window (get-buffer-window ispell-choices-buffer)))
...
;; Overlay *Choices* window when it isn't showing
(ispell-overlay-window (max line ispell-choices-win-default-height)))
(switch-to-buffer ispell-choices-buffer)
(goto-char (point-min)))))
does strange things when `switch-to-buffer' does _not_ use the window
selected by `ispell-overlay-window'. You can, for example, get an extra
window showing the initial buffer.
> IIUC, ispell already supports displaying the choices in another frame
> when `ispell-use-framepop-p' is non-nil, but it does this with
> an unknown function `framepop-display-buffer'.
We have to rewrite ispell's window handling from scratch.
martin
next prev parent reply other threads:[~2011-11-04 9:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 19:03 bug#3419: 23.0.94; calc, calendar and temp-buffer-resize-mode Leo
2009-05-29 23:46 ` Jay Belanger
2009-05-30 1:43 ` Leo
2009-05-30 2:15 ` Jay Belanger
2009-05-30 9:51 ` martin rudalics
2009-05-30 10:58 ` Leo
2009-05-30 12:19 ` martin rudalics
2009-05-30 18:21 ` Glenn Morris
2009-05-30 22:37 ` Leo
2011-10-24 11:07 ` Leo
2011-10-24 16:15 ` martin rudalics
2011-10-25 2:17 ` Leo
2011-10-25 2:47 ` Jay Belanger
2011-10-25 15:20 ` Leo
2011-10-31 10:34 ` Juri Linkov
2011-10-31 18:56 ` Jay Belanger
2011-11-01 9:27 ` Juri Linkov
2011-11-01 14:38 ` martin rudalics
2011-11-01 20:00 ` Stefan Monnier
2011-11-01 21:54 ` Juri Linkov
2011-11-02 1:21 ` Stefan Monnier
2011-11-02 9:35 ` Juri Linkov
2011-11-02 10:04 ` martin rudalics
2011-11-03 9:05 ` Juri Linkov
2011-11-03 10:07 ` martin rudalics
2011-11-03 10:17 ` Juri Linkov
2011-11-03 12:26 ` Stefan Monnier
2011-11-03 19:44 ` Juri Linkov
2011-11-03 21:07 ` Stefan Monnier
2011-11-04 9:38 ` Juri Linkov
2011-11-04 9:39 ` martin rudalics
2011-11-04 10:12 ` Juri Linkov
2011-11-04 13:55 ` martin rudalics
2011-11-03 13:59 ` martin rudalics
2011-11-03 19:45 ` Juri Linkov
2011-11-04 9:39 ` martin rudalics [this message]
2011-11-04 13:12 ` Stefan Monnier
2011-11-06 21:09 ` Jay Belanger
2011-11-02 12:37 ` Stefan Monnier
2009-06-02 15:57 ` Leo
2009-06-02 19:20 ` Jay Belanger
2009-06-02 21:28 ` Leo
2012-10-04 13:18 ` martin rudalics
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=4EB3B2B9.9010808@gmx.at \
--to=rudalics@gmx.at \
--cc=3419@debbugs.gnu.org \
--cc=juri@jurta.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.