From: Eric S Fraga <email@example.com> To: Timothy <firstname.lastname@example.org> Cc: org-mode-email <email@example.com> Subject: Re: [PATCH] Fontification for inline src blocks Date: Thu, 02 Dec 2021 12:53:40 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Timothy's message of "Mon, 22 Nov 2021 19:52:54 +0800") Timothy, I am happy to see the fontification of inline src blocks in org. Thank you! However, I am finding the result not very pleasing unfortunately. Specifically, I am not happy with the use of other pre-existing faces (shadow and org-meta-line) for this purpose. These other faces have their specific uses and the resulting combination for inline src blocks, for me, is ugly. I do not wish to modify those faces for this use case as it will affect their use everywhere else. Philosophically, the language element in an inline src block is not a /meta line/, at least not in my view: it's not even a line... 😉 Would it be possible to create new faces specifically for the various bits you want to differentiate, e.g. org-inline-src-block-language? I don't mind if they have the defaults to be the same as org-meta-line and org-shadow etc. but at least I can customise them separately. Thanks again, eric -- : Eric S Fraga, with org release_9.5.1-231-g6766c4 in Emacs 29.0.50 : Latest paper written in org: https://arxiv.org/abs/2106.05096
next prev parent reply other threads:[~2021-12-02 12:58 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 15:00 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 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 [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] Fontification for inline src blocks' \ /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 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).