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: Tue, 4 Oct 2022 16:58:01 +0000 [thread overview]
Message-ID: <81dba0dd-ed05-21d3-a827-acf938af1de4@posteo.eu> (raw)
In-Reply-To: <8735d768ov.fsf@localhost>
Hi,
Ihor Radchenko writes:
> 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.
Perhaps something like
#+... name: A classic tag: easy
might be used for any kind of keyword. That'd be quite the trick.
It would certainly improve the situation when an element has several
keywords, but I'm not sure how common that is.
I'll look into implementing such #+name and #+tag keywords, when I
have the time.
On an unrelated note, how is your work on revamping org's
fontification going, if I may ask ? I had had a look at your repo, but
since adapting my configuration would have required some effort I did
not try it.
--
Sébastien Miquel
next prev parent reply other threads:[~2022-10-04 17:33 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
2022-10-04 16:58 ` Sébastien Miquel [this message]
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=81dba0dd-ed05-21d3-a827-acf938af1de4@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).