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: Sun, 10 Sep 2023 11:48:31 +0100 [thread overview]
Message-ID: <ZP2e/wc1K5JBZXW3@itccanarias.org> (raw)
In-Reply-To: <87h6o2jv8y.fsf@localhost>
On Sun, Sep 10, 2023 at 08:19:25AM +0000, Ihor Radchenko wrote:
> (defun my-org-capture-kill-buffer ()
> (when (equal current-prefix-arg '(16))
> (save-excursion
> (org-capture-goto-last-stored)
> (kill-buffer))))
Thanks for the proposed solution. I have tried it and it didn't work for me. Or
it worked somehow. If it kills the buffer, then the buffer is opened again
right after it is killed, jumping to the last stored position. I think this is
because of the way the 'org-capture-finalize' function is implemented:
...
(cond
(abort-note
(cl-case abort-note
(clean
(message "Capture process aborted and target buffer cleaned up"))
(dirty
(error "Capture process aborted, but target buffer could not be \
ned up correctly"))))
(stay-with-capture ;; <- this cond is executed
(org-capture-goto-last-stored)))
...
It seems that the 'org-capture-goto-last-stored' function is called after the
hooks so the buffer is opened again.
This is just my interpretation. I'm not an expert in elisp.
next prev parent reply other threads:[~2023-09-10 10:49 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
2023-09-10 8:19 ` Ihor Radchenko
2023-09-10 10:48 ` Eduardo Suarez [this message]
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=ZP2e/wc1K5JBZXW3@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).