From: Vincent Lefevre <vincent@vinc17.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50640@debbugs.gnu.org, Alan Mackenzie <acm@muc.de>,
Stefan Kangas <stefan@marxist.se>
Subject: bug#50640: 28.0.50; incorrect highlighting in C++ mode
Date: Fri, 26 Aug 2022 14:24:08 +0200 [thread overview]
Message-ID: <20220826122408.GH61030@zira.vinc17.org> (raw)
In-Reply-To: <87k06vcjtr.fsf@gnus.org>
On 2022-08-26 13:42:24 +0200, Lars Ingebrigtsen wrote:
> Alan Mackenzie <acm@muc.de> writes:
>
> > There's really not much which can be done about this in CC Mode, sorry.
> > CC Mode's analysis of ambiguous C++ constructs is not very deep, so it
> > sometimes gets it wrong, as here.
> >
> > I would be in favour of closing this bug as "won't fix" (actually, can't
> > fix).
>
> OK; closing this as a "wontfix", then.
Isn't it really possible to have an option to forbid && and ||
in <...> constructs?
I think that this would be useful in practice, because when && or ||
is involved, < and > around them probably mean comparisons.
Note that the issue is more general than nested < .. < .. > .. >.
Bad highlighting also occurs just with "a < b || c > d".
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
prev parent reply other threads:[~2022-08-26 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 12:57 bug#50640: 28.0.50; incorrect highlighting in C++ mode Vincent Lefevre
2021-09-25 18:17 ` Stefan Kangas
2021-09-25 21:17 ` Alan Mackenzie
2021-09-25 21:51 ` Vincent Lefevre
2022-08-26 11:42 ` Lars Ingebrigtsen
2022-08-26 12:24 ` Vincent Lefevre [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:
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=20220826122408.GH61030@zira.vinc17.org \
--to=vincent@vinc17.net \
--cc=50640@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).