unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: 72068@debbugs.gnu.org, Siyuan Chen <chansey97@gmail.com>
Subject: bug#72068: show-paren-mode does not match Chinese parentheses correctly
Date: Wed, 24 Jul 2024 13:11:37 -0700	[thread overview]
Message-ID: <CADwFkmkyV+8PiQAtVNAv_BAG7VokxY4H0c3LzeZ0pQ96oYKZaw@mail.gmail.com> (raw)
In-Reply-To: <jwvy1664w6w.fsf-monnier+emacs@gnu.org>

severity 72068 wishlist
thanks

Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:

> Eli Zaretskii [2024-07-12 09:02:49] wrote:
>> I'm not sure this is a bug, since I think Lisp allows those characters
>> to be treated as symbol-constituent.  Stefan, am I right?
>
> I think that's the idea, indeed.  Of course, we don't have to obey the
> Emacs Lisp syntax, but I think it makes sense to do so.
> Admittedly, it would be nice to allow the use of other syntax rules inside
> comments and string for these kinds of situations.

I'm not sure if this should be closed as notabug or not, but I'm tagging
it as wishlist at least.  Feel free to close if that makes more sense.





  reply	other threads:[~2024-07-24 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12  5:03 bug#72068: show-paren-mode does not match Chinese parentheses correctly Siyuan Chen
2024-07-12  6:02 ` Eli Zaretskii
2024-07-12 12:45   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 20:11     ` Stefan Kangas [this message]
2024-07-25  5:20       ` Eli Zaretskii
2024-07-25 11:34         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-01  1:10           ` Dmitry Gutov

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=CADwFkmkyV+8PiQAtVNAv_BAG7VokxY4H0c3LzeZ0pQ96oYKZaw@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=72068@debbugs.gnu.org \
    --cc=chansey97@gmail.com \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).