From: Protesilaos Stavrou <public@protesilaos.com>
To: Ihor Radchenko <yantar92@gmail.com>, Timothy <tecosaur@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Fontification for inline src blocks
Date: Mon, 04 Oct 2021 23:02:50 +0300 [thread overview]
Message-ID: <87pmskr21h.fsf@protesilaos.com> (raw)
In-Reply-To: <87r1d25vbl.fsf@localhost>
On 2021-10-03, 17:09 +0800, Ihor Radchenko <yantar92@gmail.com> wrote:
> Timothy <tecosaur@gmail.com> writes:
>
>> Ihor Radchenko <yantar92@gmail.com> writes:
>>
>>> Let me bump this thread again and mark it as a patch ;)
>>
>> Thanks for the bump. I'd like to get this working, but I don't know how best to
>> deal with the "prettification" of {{{results(=value=)}}}, which is the major blocker as I
>> see it.
>
> What about separating the src_{} fontification into separate patch? I
> think that part raised no objections.
>
> As for the results prettifications, I look at this and similar ideas as
> at Emacs themes. It looks nice on your screenshot with your fonts and
> colours, but may not be good for other people. Similar to org-bullets
> and co.
>
> I can see how some people (I am among those people) want to reduce the
> markup noise beyond hiding emphasis markers. However, some people
> prefer not to hide text in buffer under "bells and whistles". Maybe we
> can create some kind of "prettify-symbol themes" replacing different
> markup elements in bulk with nice symbols/svg (e.g. inline results,
> block headers/footers, uninteresting property drawers aka
> org-custom-properties, bullets, etc)?
> WDYT?
>
> Also, CCing Prot as it might be of interest for him.
Thank you!
I am monitoring the discussion in case there is something I would need
to do for my themes. Otherwise I have no technical insight to offer
about the substance of this feature.
With regard to the use of faces, I generally find that re-purposing
faces in an altogether different context than their original can create
constraints for users/themes. For example, and without having tried the
patch yet, we find this:[1]
(font-lock-append-text-property beg lang-end 'face 'org-block)
Is the text-to-be-propertised the same as an Org block or does it differ
in purpose/presentation? Because a user/theme may like their blocks to
e.g. have no background of their own, but also wish to maintain a
distinct background colour for inline constructs like org-verbatim,
org-code, and those discussed here. The rationale would be that blocks
are clear enough due to their innate spacing and indentation, whereas
inline constructs are surrounded by text.
This is not a hard requirement, of course, while too many overly
specific faces can also prove problematic for testing/maintenance. Just
something for you to bear in mind.
Finally, how does the use of 'org-block' in this context relate to
'org-src-block-faces'? Could there be undesired conflicts in styling or
whatnot?
All the best,
Prot
[1] <https://list.orgmode.org/87pmzf4bd0.fsf@gmail.com/>
--
Protesilaos Stavrou
https://protesilaos.com
next prev parent reply other threads:[~2021-10-04 20:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 15:00 [PATCH] Fontification for inline src blocks Timothy
2021-04-28 7:14 ` Timothy
2021-05-02 20:17 ` Timothy
2021-05-02 20:57 ` Tom Gillespie
2021-05-02 21:03 ` Timothy
2021-05-02 21:13 ` Tom Gillespie
2021-05-02 23:54 ` Tom Gillespie
2021-05-03 3:29 ` Timothy
2021-05-12 11:15 ` Timothy
2021-05-12 14:24 ` Ihor Radchenko
2021-05-12 14:47 ` Timothy
2021-05-12 15:53 ` Ihor Radchenko
2021-05-12 16:39 ` Timothy
2021-05-13 2:38 ` Tim Cross
2021-05-13 5:31 ` Ihor Radchenko
2021-05-18 12:06 ` Sébastien Miquel
2021-05-18 13:34 ` Timothy
2021-05-18 14:36 ` Sébastien Miquel
2021-04-29 22:59 ` TRS-80
2021-10-03 7:14 ` Ihor Radchenko
2021-10-03 7:16 ` Timothy
2021-10-03 9:09 ` Ihor Radchenko
2021-10-03 9:22 ` Timothy
2021-10-04 20:02 ` Protesilaos Stavrou [this message]
2021-11-21 14:09 ` Timothy
2021-11-22 11:52 ` Timothy
2021-11-22 12:23 ` Ihor Radchenko
2021-11-22 13:43 ` Timothy
2021-11-22 14:35 ` Ihor Radchenko
2021-11-22 14:37 ` Timothy
2021-11-23 13:30 ` Ihor Radchenko
2021-11-29 19:21 ` Timothy
2021-11-30 11:44 ` Timothy
2021-11-30 12:45 ` Sébastien Miquel
2021-11-30 12:46 ` Timothy
2021-11-30 12:21 ` Ihor Radchenko
2021-12-02 12:53 ` Eric S Fraga
2021-12-02 13:57 ` Faces for inline src blocks (was: [PATCH] Fontification for inline src blocks) Timothy
2021-12-02 15:52 ` Faces for inline src blocks Eric S Fraga
2021-12-02 15:56 ` Timothy
2021-12-02 16:15 ` Eric S Fraga
2021-11-23 10:45 ` [PATCH] Fontification " Vitaly Ankh
2021-11-23 13:45 ` Vitaly Ankh
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=87pmskr21h.fsf@protesilaos.com \
--to=public@protesilaos.com \
--cc=emacs-orgmode@gnu.org \
--cc=tecosaur@gmail.com \
--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).