From: Ihor Radchenko <yantar92@gmail.com>
To: Christian Heinrich <com-orgmode-mailinglist@gladbachcity.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-capture and fast selection of tags
Date: Sat, 16 Jul 2022 17:12:47 +0800 [thread overview]
Message-ID: <87a699e7zk.fsf@localhost> (raw)
In-Reply-To: <c146576791b4b39c451d9d6c7a1e120c298f14e7.camel@gladbachcity.de>
Christian Heinrich <com-orgmode-mailinglist@gladbachcity.de> writes:
> I looked at the code and came up with a patch that works for me (see below). However, this may
> change behavior for others:
Thanks!
> 1. The original %^g will work on non-headlines, but if (org-set-tags-command) is called as I do,
> this is no longer possible and would need to be checked (what would be a good way here?)
>
> 2. Can I really deduce from (org-use-fast-tag-selection) being non-nil that fast selection should be
> used in capture templates as well? Does it actually make sense to incorporate this into %^g/G?
>
> I am neither a lisp programmer nor acquainted with the org codebase; this is a draft I came up
> with. If you can provide me with further feedback, I'm willing to make this more stable.
The idea is reasonable, but using org-set-tags-command is not ideal
indeed. Instead, you can take the relevant part of org-set-tags-command
(it is all but last line of the "t" cond clause) and put it into a
separate auxiliary function. Then, you can simply call that function
inside the org-set-tags-command and inside the capture template code.
Best,
Ihor
next prev parent reply other threads:[~2022-07-16 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 9:32 org-capture and fast selection of tags Christian Heinrich
2022-07-11 2:02 ` Ihor Radchenko
2022-07-14 10:12 ` Christian Heinrich
2022-07-16 9:12 ` Ihor Radchenko [this message]
2022-07-16 15:03 ` Christian Heinrich
2022-07-17 10:14 ` Ihor Radchenko
2022-08-23 2:17 ` Ihor Radchenko
2022-09-28 18:40 ` Christian Heinrich
2022-09-29 3:57 ` Ihor Radchenko
2023-04-02 10:21 ` Ihor Radchenko
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=87a699e7zk.fsf@localhost \
--to=yantar92@gmail.com \
--cc=com-orgmode-mailinglist@gladbachcity.de \
--cc=emacs-orgmode@gnu.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).