From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Kaushal <kaushal.modi@gmail.com>
Cc: emacs-orgmode@gnu.org, Charles Millar <millarc@verizon.net>
Subject: Re: [feature request] org-capture-window-setup to stop capture window taking up whole frame
Date: Wed, 17 Jun 2015 09:24:30 +0100 [thread overview]
Message-ID: <874mm6pwsh.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <CAFyQvY2MnozqPMZ6gfqC7tu6L3+PCXEZ1W6BMsopLUSzZA2v8A@mail.gmail.com> (Kaushal's message of "Mon, 08 Jun 2015 16:46:13 +0000")
On Monday, 8 Jun 2015 at 16:46, Kaushal wrote:
> `org-capture` does not take up the full frame for me by default; I just
> tried that in an emacs -Q session.
Okay, I have finally found some time to get back to this (been marking
exam scripts, for my sins... ;-).
If the capture template prompts for information, the whole frame is
cleared and only the bare capture buffer is shown in the frame while the
prompts are processed. This is my main problem: I often want to include
some information from the existing buffers in my org capture and all the
information is hidden just when I want it.
Once the prompts have been answered, the windows shown in the frame
change with the original window present as well as the capture
window. This is too late.
All of the above confirmed with emacs -Q.
The question, I guess, is why does org-capture need to take over the
whole frame while processing the prompts in the capture template? If it
needs to display the capture buffer while handling the prompts, why not
display it as it will once the prompts have been processed?
Thanks,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-1216-gb856f6
next prev parent reply other threads:[~2015-06-17 8:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 15:23 [feature request] org-capture-window-setup to stop capture window taking up whole frame Eric S Fraga
2015-06-08 16:37 ` Charles Millar
2015-06-08 16:46 ` Kaushal
2015-06-09 7:31 ` e.fraga
2015-06-17 8:24 ` Eric S Fraga [this message]
2015-06-17 16:41 ` Subhan Michael Tindall
2015-06-18 7:57 ` Eric S Fraga
2015-06-23 20:31 ` Nicolas Goaziou
2015-06-25 8:00 ` Eric S Fraga
2015-06-25 12:22 ` Nicolas Goaziou
2015-06-08 20:28 ` Thierry Banel
2015-06-09 9:22 ` Alan Schmitt
2015-06-09 9:43 ` Eric S Fraga
2015-06-18 11:16 ` Xebar Saram
2015-06-18 11:45 ` Alan Schmitt
2015-06-18 11:52 ` Xebar Saram
2015-06-18 14:42 ` Alan Schmitt
[not found] ` <871thlw193.fsf@gmail.com>
2015-06-09 12:35 ` Bernhard Pröll
2015-06-12 9:27 ` Eric S Fraga
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=874mm6pwsh.fsf@delle7240.chemeng.ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=millarc@verizon.net \
/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).