From: Christoph Groth <cwg@falma.de>
To: emacs-orgmode@gnu.org
Subject: Re: org-capture: keeping window visible during date entry
Date: Sat, 07 Jul 2012 19:58:08 +0200 [thread overview]
Message-ID: <87d34778sv.fsf@falma.de> (raw)
In-Reply-To: CAJcAo8ta_yUT3q3f=+YVPv+d0p_vx1RFSES23EJFHjA8CRdd6w@mail.gmail.com
Samuel Wales <samologist@gmail.com> writes:
> On 7/7/12, Christoph Groth <cwg@falma.de> wrote:
>> I would say that a proper solution would be to reserve
>> delete-other-windows for interactive use and to replace it by
>> something more sensible which ensures that a given window is well
>> visible but tries to preserve the visibility and arrangement other
>> windows if possible. That hypothetical function could be given the
>> minimum required height for the current window.
>
> This is something that needs to be under user control. We cannot
> force a regression on an accessibility issue. Not all screen sizes
> are large and not all fonts are small.
My proposal is not about reducing accessibility but increasing
usability.
What's the point of deleting all the other windows to show a buffer
containing only five lines of text (a typical capture buffer) and
unlikely to grow much? If the user wants to type a lot into the new
buffer, he can press C-x 1 himself.
By "something more sensible" I meant functionality which would do the
right thing both for small and large emacs frames. In many cases a
reasonable minimum size for the new window to be displayed can be
estimated.
My font is actually not small and my screen typical. Still, my emacs
frame is 70 lines high.
next prev parent reply other threads:[~2012-07-07 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 9:03 org-capture: keeping window visible during date entry Christoph Groth
2012-06-16 7:14 ` Eric Abrahamsen
2012-07-07 15:24 ` Christoph Groth
2012-07-07 16:40 ` Samuel Wales
2012-07-07 17:58 ` Christoph Groth [this message]
2012-07-07 18:48 ` Samuel Wales
2012-08-08 11:17 ` Bastien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d34778sv.fsf@falma.de \
--to=cwg@falma.de \
--cc=emacs-orgmode@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).