From: Max Nikulin <manikulin@gmail.com>
To: "Léo Ackermann" <leo.komba@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Conflict between org-emphasis and org-latex
Date: Thu, 30 Sep 2021 21:48:41 +0700 [thread overview]
Message-ID: <a2863f47-ad76-74d6-dec6-7173149d0a39@gmail.com> (raw)
In-Reply-To: <8A4CA190-3AB8-462A-AF37-65985491C0DF@gmail.com>
On 27/09/2021 00:05, Léo Ackermann wrote:
>> Le 26 sept. 2021 à 19:01, Timothy a écrit :
>> You write:
>>> Nevertheless, I think that this bug has been introduced recently (I never noticed it before) and has to be corrected properly (as this is a really basic use of
>>> org-mode).
>>> Unfortunately, I can barely understand elisp... so writing a patch is far away from what I can do :/
>>
>> Do you think you might be able to identify a "good" commit and bisect
>> the bug? That would be a tremendous help for solving it, and shouldn't
>> require any elisp.
It is not bisect, though results for "emacs -Q" or "emacs -q" are
identical for the following Org versions:
- Org mode version 9.5 (release_9.5-6-g59cb39 ...) - current main
- Org mode version 9.3.1 (9.3.1-dist ...) - elpa-org package from
Ubuntu-20.04
- Org mode version 9.1.9 (release_9.1.9-65-g5e4542 ...) - bundled with
emacs-26.3 Ubuntu-20.04 package
- "and" is bold in the buffer (wrong)
- Export to LaTeX (correct): "Consider \(a^{*}\) and \(b^{*}\)"
I do not think that some problem has been introduced recently.
next prev parent reply other threads:[~2021-09-30 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 12:24 [BUG] Conflict between org-emphasis and org-latex Léo Ackermann
2021-09-26 12:57 ` Juan Manuel Macías
2021-09-26 16:57 ` Léo Ackermann
2021-09-26 17:01 ` Timothy
2021-09-26 17:05 ` Léo Ackermann
2021-09-26 17:07 ` Timothy
2021-09-30 14:48 ` Max Nikulin [this message]
2021-09-26 18:29 ` Juan Manuel Macías
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=a2863f47-ad76-74d6-dec6-7173149d0a39@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=leo.komba@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).