From: Payas Relekar <relekarpayas@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] Add option for category to be derived from #+TITLE instead of file name [9.6 ( @ /nix/store/jv2kmcbm79k4g6i778hblw98l0pxxghf-emacs-packages-deps/share/emacs/site-lisp/elpa/org-9.6/)]
Date: Sat, 03 Dec 2022 13:01:47 +0530 [thread overview]
Message-ID: <875yetdjqd.fsf@gmail.com> (raw)
Payas Relekar <relekarpayas@gmail.com> writes:
> After discovering categories
> (https://orgmode.org/manual/Categories.html) I'd like to use them
> everywhere because it makes agenda cleaner. But currently, it has only
> below options to get this value (in order of precedence, highest to lowest)
>
> - #+CATEGORY property (if present)
> - file name
>
> While I can set the property in my capture templates, it will only take
> effect on newly created files and will not retroactively apply all the
> previously created ones.
>
> As such, I'd like to propose adding variable to allow user to specify
> whether #+TITLE property should be preferred over #+CATEGORY. The
> default can continue as is, but if the user chooses to perfer title,
> order of preference will look like (highest to lowest):
>
> - #+TITLE (if present)
> - #+ CATEGORY (if present)
> - file name
Actually this is a mistake. It should always prefer explicit property
(#+CATEGORY) over implicit (#+TITLE). So the order should look like (if
the user modifies the variable, highest to lowest):
- #+CATEGORY (if present)
- #+TITLE (if present AND if user sets the variable)
- file name
Apologies for confusion.
Thanks,
Payas
--
next reply other threads:[~2022-12-03 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 7:31 Payas Relekar [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-03 7:19 [BUG] Add option for category to be derived from #+TITLE instead of file name [9.6 ( @ /nix/store/jv2kmcbm79k4g6i778hblw98l0pxxghf-emacs-packages-deps/share/emacs/site-lisp/elpa/org-9.6/)] Payas Relekar
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=875yetdjqd.fsf@gmail.com \
--to=relekarpayas@gmail.com \
--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).