emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Payas Relekar <relekarpayas@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Support for tagging (special) blocks
Date: Thu, 01 Sep 2022 14:13:37 +0800	[thread overview]
Message-ID: <87ler3oc4u.fsf@localhost> (raw)
In-Reply-To: <8735dbbuku.fsf@gmail.com>

Payas Relekar <relekarpayas@gmail.com> writes:

> Tags are bit more generic though, and allow searching across not just
> code blocks, but TODOs as well.

They do not. Tags are only considered inside headlines. Trying to allow
tags outside headlines will require major changes across the whole Org
codebase and will still make things incompatible with third party
packages, like org-ql. Not to mention the whole new concept for block
syntax.

If one wants to add "tags" or other keywords associated with blocks or
other Org elements, the right tool to use is affiliated keywords. But
note that Org search infrastructure is tailored towards searching
headlines.

-- 
Ihor Radchenko,
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


  reply	other threads:[~2022-09-01  6:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  4:13 Support for tagging (special) blocks Payas Relekar
2022-09-01  6:13 ` Ihor Radchenko [this message]
2022-09-01 16:40   ` Sébastien Miquel
2022-09-02 13:11     ` Ihor Radchenko
2022-09-02 15:32       ` Sébastien Miquel
2022-09-03  8:41         ` Ihor Radchenko
2022-09-03 10:00           ` Sébastien Miquel
2022-09-04  4:54             ` Ihor Radchenko
2022-10-04 16:58               ` Sébastien Miquel
2022-10-05  7:49                 ` Ihor Radchenko
  -- strict thread matches above, loose matches on Subject: below --
2022-08-31 20:10 Sébastien Miquel
2022-08-31 20:38 ` Kaushal Modi
2022-09-01  6:59 ` Fraga, Eric

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=87ler3oc4u.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=relekarpayas@gmail.com \
    /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).