From: Miles Bader <miles@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Stefan Monnier' <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: face-remap.el patch to resize window
Date: Tue, 11 Aug 2009 01:52:10 +0900 [thread overview]
Message-ID: <87bpmnbohx.fsf@catnip.gol.com> (raw)
In-Reply-To: <91793771320945CAA5CA2B600D0E9B67@us.oracle.com> (Drew Adams's message of "Mon, 10 Aug 2009 09:31:47 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
>> It could be useful for very specific cases,
>> but it seems somehow wrong to have it as a global setting.
>
> No reason given? What good to others is a judgment with no supporting
> rationale, arguments or evidence?
The main problem is that I think it often depends on the buffer contents
(or etc) as to whether such window-adaptation is useful.
For instance, I shrink text for several reasons:
1) To see more of the buffer at once; in this case, I probably don't
want the window to shrink. This is probably the most common case
for me.
2) To shrink a short buffer to take up less space, e.g. a help buffer;
in this case, I often do want the window to shrink, or even better,
to be re-fit to the buffer contents (like the help display
functions do initially).
3) To shrink a buffer that I want to keep on screen so I can keep an
eye on it, but in many cases, only really care about the last
bit -- e.g., a compile buffer, or log buffer which is being
updated. Often my goal is to make the window showing this buffer
as small as possible or a little larger. [and I often shrink the
font to some absurdly small size, since I care more about motion
and text-shape than actual contents]
So, really I want the behavior to vary depending on the situation; a
single "adapt windows" or "don't adapt windows" doesn't really suffice
for my usage. However, a "clever" function that encodes my preferences
(as noted above) might be something I'd like to use.
That's why I like a hook-based situation (see earlier patch) that can
examine the situation and do something appropriate in an easily
user-adaptable way.
-Miles
--
P.S. All information contained in the above letter is false,
for reasons of military security.
next prev parent reply other threads:[~2009-08-10 16:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 1:04 face-remap.el patch to resize window Drew Adams
2009-08-10 3:00 ` Stefan Monnier
2009-08-10 3:27 ` Drew Adams
2009-08-10 5:04 ` Miles Bader
2009-08-10 17:00 ` Drew Adams
2009-08-10 3:34 ` Miles Bader
2009-08-10 15:01 ` Stefan Monnier
2009-08-10 16:31 ` Drew Adams
2009-08-10 16:52 ` Miles Bader [this message]
2009-08-10 16:59 ` Drew Adams
2009-08-10 17:16 ` Stefan Monnier
2009-08-10 17:00 ` Stefan Monnier
2009-08-10 17:15 ` Drew Adams
2009-08-10 17:37 ` Miles Bader
2009-08-10 21:41 ` Drew Adams
2009-08-10 18:03 ` Stefan Monnier
2009-08-10 21:50 ` Drew Adams
2009-08-11 3:45 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2009-06-29 22:10 Drew Adams
2009-06-22 20:40 Drew Adams
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=87bpmnbohx.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.