From: Ihor Radchenko <yantar92@gmail.com>
To: sebastien.miquel@posteo.eu
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Support for tagging (special) blocks
Date: Sat, 03 Sep 2022 16:41:25 +0800 [thread overview]
Message-ID: <87ler097ey.fsf@localhost> (raw)
In-Reply-To: <8f79980b-e903-c68a-cf07-6c5265215ee4@posteo.eu>
Sébastien Miquel <sebastien.miquel@posteo.eu> writes:
> > We already have ":exports none" header argument.
>
> For src block yes, but not for special blocks.
>
> To explain where I'm coming from : I write mathematical content
> categorized using special blocks, such as theorems, exercices, proofs,
> personnal notes, etc. Then from a single org file, I export several
> pdf files, filtering the content according to the types and tags of
> special blocks : for example, to exclude some proofs, or exercices
> that are too hard.
We may allow something like
#+attr_all: :exports no
in export.
> > Affiliated keywords are indeed not uniform with headlines. But they are
> > uniform with everything else. Paragraphs can have affiliated keywords.
> > Or other blocks. Or lists. Or tables...
>
> That's indeed a good point. In fact, I had been wondering recently how
> I could tag a single list item, but I guess affiliated keywords still
> can't do that.
Affiliated keywords can be assigned to lists. Not single items though:
#+CAPTION: test1
- item 1
#+CAPTION: test2
- item 2
#+CAPTION: test3
- item 3
> >> On a slightly related note, I find it quite unfortunate that one
> >> presently cannot make use of the #+begin_ line of special blocks to
> >> set some kind of optional title instead of using #+name or
> >> #+attr_latex. That's a lot of wasted real estate.
> >
> > Yes, but we do not want to overcomplicate Org syntax. Affiliated
> > keywords are universal across multiple element types. Adding a
> > specialized syntax for src blocks will make things complex technically
> > and create duplicate code.
> >
> > We can alter the fontification to compact the screen space though. Will
> > it suffice?
> >
>
> I don't see any possible compactification that doesn't hinder
> readability. From my perspective, it is important that the type of the
> special block, its title, and its tags are readable.
I feel that I either misunderstand you here or in the previous message.
--
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
next prev parent reply other threads:[~2022-09-03 8:41 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ler097ey.fsf@localhost \
--to=yantar92@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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.