emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Kaushal Modi <kaushal.modi@gmail.com>
To: sebastien.miquel@posteo.eu
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Support for tagging (special) blocks
Date: Wed, 31 Aug 2022 16:38:53 -0400	[thread overview]
Message-ID: <CAFyQvY1vDOMQa4VwTssNgj2G7s5Q4Rj=QmybjvqQBnBFkKp89Q@mail.gmail.com> (raw)
In-Reply-To: <a14fff37-3d8f-29fa-ed72-7d12784a4774@posteo.eu>

[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]

On Wed, Aug 31, 2022 at 4:19 PM Sébastien Miquel <sebastien.miquel@posteo.eu>
wrote:

> Hi,
>
> I've been using tags on special blocks, src blocks and other, for two
> purposes:
>
>   1. to control which blocks get exported, using the `#+exclude_tags`
>      property.
>   2. to fine tune the export, according to tags, of special blocks such as
>      #+BEGIN_exercice                                            :hard:
>      …
>      #+END_exercice
>
> Does anyone think this is useful and might warrant adding support for ?
>

I think that using the #+header: property for something like this might be
more canonical.
https://orgmode.org/manual/Using-Header-Arguments.html

Example:

=====
#+header: :tags noexport
#+begin_foo
..
#+end_foo
=====

or

=====
#+header: :tags hard
#+begin_foo
..
#+end_foo
=====

It's also relatively easy to parse these headers:

=====
(org-babel-parse-header-arguments (car (org-element-property :header
special-block)))
=====

[-- Attachment #2: Type: text/html, Size: 1757 bytes --]

next prev parent reply	other threads:[~2022-08-31 20:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 20:10 Support for tagging (special) blocks Sébastien Miquel
2022-08-31 20:38 ` Kaushal Modi [this message]
2022-09-01  6:59 ` Fraga, Eric
  -- strict thread matches above, loose matches on Subject: below --
2022-09-01  4:13 Payas Relekar
2022-09-01  6:13 ` Ihor Radchenko
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

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='CAFyQvY1vDOMQa4VwTssNgj2G7s5Q4Rj=QmybjvqQBnBFkKp89Q@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastien.miquel@posteo.eu \
    /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

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).