unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ikumi Keita <ikumi@ikumi.que.jp>
To: emacs-devel@gnu.org
Cc: Markus Kohm <komascript@gmx.info>, 35140@debbugs.gnu.org
Subject: Re: bug#35140: 12.1; Scan errors in doctex mode with ^^A-comments after braces
Date: Wed, 02 Mar 2022 18:01:18 +0900	[thread overview]
Message-ID: <26626.1646211678@localhost> (raw)
In-Reply-To: <24961.1646146234@localhost>

Greetings, Emacs developers.

I'd like to ask what to do with bug#35140. This was originally posted as
AUCTeX bug, but the same issue applies for Emacs built-in tex-mode.el as
well, as described below. That's the reason why I'm posting to
emacs-devel.

Please have a look at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35140#5
to see what this bug is.

The reason of this error is the syntax-table property put on the closing
curly brace. In order to achieve different fontification on the docTeX
documentation and the comment after ^^A, the function
`font-latex-doctex-^^A' puts the "comment ender" syntax on the closing
"}", which hides the proper syntax "closing paren paired with {" and
thus leads to the reported error.

Actually, `font-latex-doctex-^^A' is essentially just a copy of
`doctex-font-lock-^^A' in `tex-mode.el', so the Emacs built-in
doctex-mode shares exactly the same problem with respect to the given
test file at double-clicking.

Are there any smart ways to address this issue?

Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine



       reply	other threads:[~2022-03-02  9:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1990475.NB1R35vEMU@komascript.de>
     [not found] ` <25610.1557200375@localhost>
     [not found]   ` <12115.1646127291@localhost>
     [not found]     ` <86pmn5j3eg.fsf@gnu.org>
     [not found]       ` <24961.1646146234@localhost>
2022-03-02  9:01         ` Ikumi Keita [this message]
2022-03-02 14:01           ` bug#35140: 12.1; Scan errors in doctex mode with ^^A-comments after braces Stefan Monnier

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=26626.1646211678@localhost \
    --to=ikumi@ikumi.que.jp \
    --cc=35140@debbugs.gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=komascript@gmx.info \
    /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.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).