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

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: Sun, 04 Sep 2022 12:54:24 +0800	[thread overview]
Message-ID: <8735d768ov.fsf@localhost> (raw)
In-Reply-To: <1cee88b1-00f6-44ff-be26-b43ece0c3e8b@posteo.eu>

Sébastien Miquel <sebastien.miquel@posteo.eu> writes:

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

Thanks for the clarification!
I did not mean to reduce the font size in affiliated keywords.
I was referring to replacing the display of affiliated keywords:

#+name: A classic
#+tag: easy

will be displayed by Emacs as

#+... A classic :easy:

The underlying text will not be changed.
The hidden parts will be revealed upon cursor entering the affiliated
keywords.

-- 
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-04  4:54 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
2022-09-04  4:54             ` Ihor Radchenko [this message]
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=8735d768ov.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

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