From: martin rudalics <rudalics@gmx.at>
To: jay.p.belanger@gmail.com, 3419@emacsbugs.donarmstrong.com
Subject: bug#3419: 23.0.94; calc, calendar and temp-buffer-resize-mode
Date: Sat, 30 May 2009 11:51:45 +0200 [thread overview]
Message-ID: <4A2101B1.8080106@gmx.at> (raw)
In-Reply-To: <873aanxrnd.fsf@gmail.com>
>> But I'm not sure whether this is a bug in calc or temp-buffer-resize-mode.
>
> Or neither, and simply unexpected behavior.
> I've never used temp-buffer-resize-mode before, but if it's supposed to
> make a window a better size for displaying a temporary buffer, I'm
> surprised it doesn't change anything back when the buffer is killed or
> hidden.
Changing window sizes when `temp-buffer-resize-mode' exits is tricky.
That is, we could restore the window configuration that existed when
`temp-buffer-resize-mode' was started but that has the often unwanted
side-effect that other windows created (deleted) in the meantime get
deleted (resurrected).
> In this case, I'm not sure it's Calc's job to keep track of why
> it changed its window size. Perhaps an option "Always start Calc with
> the initial window height" might be helpful.
Calc could make its windows fixed-size but that's hardly reasonable with
the current handling of fixed-size windows. Any option affecting only
the initial size of Calc windows won't help in the present case either.
We could give Calc window parameters, say ideal-height and ideal-width,
and try to use these when exiting `temp-buffer-resize-mode' but writing
the corresponding code won't be trivial.
martin
next prev parent reply other threads:[~2009-05-30 9:51 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 [this message]
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
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=4A2101B1.8080106@gmx.at \
--to=rudalics@gmx.at \
--cc=3419@emacsbugs.donarmstrong.com \
--cc=jay.p.belanger@gmail.com \
/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.