emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: problem with unwanted strikeout in src blocks
Date: Tue, 24 May 2022 14:44:54 +0200	[thread overview]
Message-ID: <87sfozt7zt.fsf@mat.ucm.es> (raw)
In-Reply-To: 87sfozsiey.fsf@localhost

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

>>> "IR" == Ihor Radchenko <yantar92@gmail.com> writes:

> Uwe Brauer <oub@mat.ucm.es> writes:
>> However when I wrap a solutionorbox around it (which I need when
>> exporting to latex) all text between the «+» 
>> gets a strikeout.
>> #+begin_solutionorbox
>> #+begin_src matlab :exports results :eval never-export :results output latex
>> disp('P(\text{Covid19}|\text{+})&=\frac{P(\text{+}|\text{Covid19})P(\text{Covid19})}{P(\text{+}|\text{Covid19})P(\text{Covid19})+P(\text{+}|\text{No-Covid19})P(\text{No-Covid19})}\\')
>> #+end_src
>> #+end_solutionorbox
>> And idea what to do?

> This is a known bug in Org fontification. The fix is not trivial. WIP.
> See https://orgmode.org/list/87ee7c9quk.fsf@localhost

Aha, thanks!
> Current development version of the fix is in
> https://github.com/yantar92/org/tree/feature/org-font-lock-element, but
> it is not yet complete and will require a lot more work.

Ok right now this is not so important for me. I might give it a try some
other time, just for testing proposes.

> Note that other than the visual appearance, your code block is not
> affected. That is, export will work just fine. No strike-through will
> be present.

That I assumed already, still it is a bit annoying, but then not that
important I say.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

      reply	other threads:[~2022-05-24 12:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 17:24 problem with unwanted strikeout in src blocks Uwe Brauer
2022-05-23 21:08 ` Jeremie Juste
2022-05-24 12:46   ` Uwe Brauer
2022-05-24  3:45 ` Ihor Radchenko
2022-05-24 12:44   ` Uwe Brauer [this message]

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:

  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=87sfozt7zt.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=emacs-orgmode@gnu.org \


* 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


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