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 17:24:21 +0200 [thread overview]
Message-ID: <87hatj7fx6.fsf@falma.de> (raw)
In-Reply-To: 87fw9vybhg.fsf@ericabrahamsen.net
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> On Thu, Jun 14 2012, Christoph Groth wrote:
>> How to ensure that the buffer which was active when org-capture was
>> executed remains visible during date entry?
> I've had the same annoyance. The attached patch is *not* a real
> solution to the problem, as it still produces some weird windowing,
> and I have no idea if it will wreck other uses of capture, but it does
> preserve gnus windows so you can see the information you're trying to
> capture. It's at least a pointer in the right direction…
Yes, the problems are mostly due to calls to delete-other-windows which
is used quite often in org (19 times) and other emacs packages as well.
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.
Does anyone know of such functionality already existing anywhere in the
emacs world? If not, I believe it would be useful to think of something
like this. Given current screen sizes, it would be good to replace most
uses of delete-other-windows by something more gentle. But this is a
topic for the general emacs mailing list.
next prev parent reply other threads:[~2012-07-07 15:24 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 [this message]
2012-07-07 16:40 ` Samuel Wales
2012-07-07 17:58 ` Christoph Groth
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=87hatj7fx6.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).