From: Eduardo Suarez-Santana <esuarez@itccanarias.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: <emacs-orgmode@gnu.org>
Subject: Re: Feature request: kill-buffer for org-capture-finalize
Date: Fri, 8 Sep 2023 13:34:15 +0100 [thread overview]
Message-ID: <ZPsUxzOT/Psy+l+1@itccanarias.org> (raw)
In-Reply-To: <87sf7o987k.fsf@localhost>
On Fri, Sep 08, 2023 at 12:10:23PM +0000, Ihor Radchenko wrote:
> Eduardo Suarez <esuarez@itccanarias.org> writes:
>
> > The function org-capture-finalize allows an argument to 'jump-to-capture'. I
> > think it may be a good idea to add a new argument to 'kill-buffer' after the
> > capture is finalized. This would be useful to avoid having to kill the capture
> > buffer manually. I assume that if ':kill-buffer' is intended as the default
> > behavior, then it would be better to set it in the capture template.
>
> May you explain a bit more about the problem you are trying to solve?
> Isn't the temporary capture buffer killed after capture already?
> Or do you refer to the org buffer where the capture is recorded?
Sorry about that. I refer to the org buffer where the capture is recorded. I
meant:
"This would be useful to avoid having to kill the target buffer manually."
I like to keep the target buffer open after the capture is finalized so I can
review the changes later, but sometimes I'd rather prefer to kill it because I
already assume that the changes are correct. This helps to keep the buffer list
clean.
next prev parent reply other threads:[~2023-09-08 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 12:03 Feature request: kill-buffer for org-capture-finalize Eduardo Suarez
2023-09-08 12:10 ` Ihor Radchenko
2023-09-08 12:34 ` Eduardo Suarez-Santana [this message]
2023-09-08 12:38 ` Ihor Radchenko
2023-09-08 12:47 ` Eduardo Suarez-Santana
2023-09-09 9:18 ` Ihor Radchenko
2023-09-09 14:11 ` Eduardo Suarez
2023-09-10 8:19 ` Ihor Radchenko
2023-09-10 10:48 ` Eduardo Suarez
2023-09-10 10:57 ` Ihor Radchenko
2023-09-10 23:17 ` Eduardo Suarez
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=ZPsUxzOT/Psy+l+1@itccanarias.org \
--to=esuarez@itccanarias.org \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.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).