From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Subject: Re: Bug: font-lock error with - in code-mode (reopened)
Date: Thu, 28 Oct 2021 21:03:34 +0700 [thread overview]
Message-ID: <8d7dd0b5-87c4-e4c5-bc76-180b6b6c2e2d@gmail.com> (raw)
In-Reply-To: <87lf3d3w6n.fsf@localhost>
This is a message to track the issue on https://updates.orgmode.org
On 01/10/2021 16:56, Ihor Radchenko wrote:
> "Dr. Arne Babenhauserheide" writes:
>
>> When parsing the following code:
>>
>> Am richtigen Ort zur richtigen Zeit (=+=; 1x pro Abenteuer im richtigen
>> Moment auftauchen), Computeraffinität (=+= oder =++=; Bonus von 3 oder 6),
>> Kurze Aufmerksamskeitsspanne (~-~), Photographisches Gedächtnis (=+=),
>> Primitive Technologie (~-~), Schreckhaft (~-~), Schrecklich Schusselig (~-~),
>> Toller Laptop (=+=) oder Verträumt (~-~).
>>
>> The fourth line is highlighted as code beginning at the first ~-~ until
>> the final closing paren (")") of the paragraph.
>
> The fix is attached.
So Ihor reverted the change by commit 52cdf53328
> Revert "org-do-emphasis-faces: Never treat closing marker as next opening marker"
>
> This reverts commit fa315986a115028d289f4921281e44e35842a27b.
>
> The commit broke fontification of nested emphasis like
> /italic *bold* more italic/.
P.S. Earlier added "yes" entry were successfully removed by my previous
message to this thread with "X-Woof-Bug: canceled" header. Hope, correct
header will be set by "X-Woof-Bug: Bug: font-lock error with - in
code-mode (reopened)"
next prev parent reply other threads:[~2021-10-28 14:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 11:46 Bug: font-lock error with - in code-mode [9.4.6 (9.4.6-gab9f2a @ /gnu/store/2pny4z6mbi2aybgzzxz0yrzkds7hbpmq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)] Dr. Arne Babenhauserheide
2021-10-01 9:56 ` Ihor Radchenko
2021-10-02 4:30 ` Bastien
2021-10-02 4:52 ` Ihor Radchenko
2021-10-02 4:59 ` Bastien
2021-10-02 5:25 ` Ihor Radchenko
2021-10-25 12:57 ` Ihor Radchenko
2021-10-25 17:33 ` Bastien
2021-10-26 6:44 ` Greg Minshall
2021-10-26 6:56 ` Bastien
2021-10-26 7:33 ` Greg Minshall
2021-10-26 17:11 ` Max Nikulin
2021-10-27 7:08 ` (Reopened) Bug: font-lock error with - in code-mode Ihor Radchenko
2021-10-27 11:50 ` Cancel "yes" entry on updates.orgmode.org (was: Re: Bug: font-lock error with - in code-mode) Max Nikulin
2021-10-27 16:51 ` Max Nikulin
2021-10-02 5:07 ` Bug: font-lock error with - in code-mode [9.4.6 (9.4.6-gab9f2a @ /gnu/store/2pny4z6mbi2aybgzzxz0yrzkds7hbpmq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)] Ihor Radchenko
2021-10-28 14:03 ` Max Nikulin [this message]
2021-10-28 14:16 ` Bug: font-lock error with - in code-mode (reopened) Ihor Radchenko
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=8d7dd0b5-87c4-e4c5-bc76-180b6b6c2e2d@gmail.com \
--to=manikulin@gmail.com \
--cc=arne_bab@web.de \
--cc=emacs-orgmode@gnu.org \
/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).