From: Ihor Radchenko <yantar92@posteo.net>
To: Eduardo Suarez-Santana <esuarez@itccanarias.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request: kill-buffer for org-capture-finalize
Date: Fri, 08 Sep 2023 12:38:07 +0000 [thread overview]
Message-ID: <87pm2s96xc.fsf@localhost> (raw)
In-Reply-To: <ZPsUxzOT/Psy+l+1@itccanarias.org>
Eduardo Suarez-Santana <esuarez@itccanarias.org> writes:
>> 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.
Did you consider :kill-buffer property in `org-capture-templates'?
:kill-buffer If the target file was not yet visited by a buffer when
capture was invoked, kill the buffer again after capture
is finalized.
Or do you mean that you sometimes want to kill the target org buffer and
sometimes not?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-09-08 12:38 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
2023-09-08 12:38 ` Ihor Radchenko [this message]
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=87pm2s96xc.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=esuarez@itccanarias.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).