From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Support for tagging (special) blocks
Date: Sat, 3 Sep 2022 10:00:24 +0000 [thread overview]
Message-ID: <1cee88b1-00f6-44ff-be26-b43ece0c3e8b@posteo.eu> (raw)
In-Reply-To: <87ler097ey.fsf@localhost>
Ihor Radchenko writes:
>> >> 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.
To clarify, here are the two alternatives I have in mind.
#+tag: easy
#+attr_latex: A classic
#+begin_exercice
Find a necessary and sufficient condition on $N$ and $P$ for $P = NP$
to hold.
#+end_exercice
#+begin_exercice A classic :easy:
Find a necessary and sufficient condition on $N$ and $P$ for $P = NP$
to hold.
#+end_exercice
In my first message, I argue that wasting two lines of my screen
hinders reading and navigating the whole org file.
I'm not sure what fontification trick you had in mind to compact the
space, but if you were thinking of making the meta lines smaller, by
say 50%, I argue in my second message that this hinders the
readability of this single exercice. The first three lines each
contain information that is important to me when I browse the file (as
opposed to information that's only relevant for org export).
The only line that contains no content information is the #+end_exercice
line, which is only here for the org parser.
--
Sébastien Miquel
next prev parent reply other threads:[~2022-09-03 10:02 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
2022-09-03 10:00 ` Sébastien Miquel [this message]
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=1cee88b1-00f6-44ff-be26-b43ece0c3e8b@posteo.eu \
--to=sebastien.miquel@posteo.eu \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).