emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eduardo Suarez <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: Sat, 9 Sep 2023 15:11:53 +0100	[thread overview]
Message-ID: <ZPx9KTb3VjaEw6Q6@itccanarias.org> (raw)
In-Reply-To: <87r0n77li4.fsf@localhost>

On Sat, Sep 09, 2023 at 09:18:27AM +0000, Ihor Radchenko wrote:
> For personal use-case, you can utilize
> `org-capture-after-finalize-hook', checking `current-prefix-arg' and
> killing the target org buffer according to the prefix argument passed.
> Then, for example, you can make C-u C-u C-c C-c unconditionally kill the
> target org buffer.

I have tried something simple like

 (defun my-org-capture-kill-buffer ()
   (when (equal current-prefix-arg '(16))
     (kill-buffer)))

as an after-finalize hook. It seems to recognize the 'current-prefix-arg'
variable.

However,

1. it looks to me that org-capture-finalize jumps to the captured item if there
are any number greater than zero of preffix arguments,

2. the code above tries to kill the buffer I was working before invoking the
capture process.

Any hint?


  reply	other threads:[~2023-09-09 14:14 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
2023-09-08 12:47       ` Eduardo Suarez-Santana
2023-09-09  9:18         ` Ihor Radchenko
2023-09-09 14:11           ` Eduardo Suarez [this message]
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=ZPx9KTb3VjaEw6Q6@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).