emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vitaly Ankh <vitalyankh@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Fontification for inline src blocks
Date: Tue, 23 Nov 2021 18:45:13 +0800	[thread overview]
Message-ID: <CAHaGBHMbRiCPnph1jmACU8D1n51YfHpd8wGpHNYGxz6EZLqXOw@mail.gmail.com> (raw)
In-Reply-To: <87o86d7g05.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]

Hi Timothy,
  It seems a great work! I'm not familiar with this yet, just curious
that if this "org-inline-src-block"
could save this problem: the preview image of inline LaTeX has a
different color from
the normal text, which is ugly and annoying. And setting
'org-format-latex-options
doesn't help because the problem is caused by the inline LaTeX using
the 'org-fixed-width face
which has a different color and when the preview image is not big
enough the color will be shown.
The attachment shows the problem where some preview LaTeX images have
different colors
surrounded.

Regards,
VitalyR


On Sun, Nov 21, 2021 at 10:16 PM Timothy <tecosaur@gmail.com> wrote:
>
> Hi All,
>
> Since the contentious component of my previous patches has been the
> `{{{results()}}}' prettification, I’ve prepared an alternate version that I’m
> hoping everybody will be fairly happy with (fingers crossed!) that tosses out
> the results prettification for now.
>
> I think Protesilaos’ comments on making some new faces deserve consideration,
> but could easily be done subsequently, as I’m quite keen to get this merged for
> now.
>
> All the best,
> Timothy

[-- Attachment #2: 2021-11-23_18-40.png --]
[-- Type: image/png, Size: 127635 bytes --]

  parent reply	other threads:[~2021-11-23 10:46 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
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   ` Vitaly Ankh [this message]
2021-11-23 13:45     ` [PATCH] Fontification " 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=CAHaGBHMbRiCPnph1jmACU8D1n51YfHpd8wGpHNYGxz6EZLqXOw@mail.gmail.com \
    --to=vitalyankh@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@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).