unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nir Friedman <quicknir@gmail.com>
Cc: 23501@debbugs.gnu.org
Subject: bug#23501: Non-regex-based syntax highlighting
Date: Tue, 10 May 2016 18:59:22 +0300	[thread overview]
Message-ID: <834ma5dhut.fsf@gnu.org> (raw)
In-Reply-To: <CA+cBnHCR4qJpkr8z3nn1k5ts5NAJc-ynkuScd+9-9QXgXfGf4g@mail.gmail.com> (message from Nir Friedman on Mon, 9 May 2016 23:12:47 -0400)

> From: Nir Friedman <quicknir@gmail.com>
> Date: Mon, 9 May 2016 23:12:47 -0400
> 
> I'm considering using emacs as a platform for C++ development. One thing that seems to lag behind on
> emacs at the moment is that all of the syntax highlighting for C++ is (as far as I can tell) regex based. This
> severely limits the accuracy and discrimination that the syntax highlighter can achieve. There are now some
> packages for emacs that use a clang based backends to get actual AST information. Perhaps it would be
> possible to write some kind of hooks or template for major modes that would make it easier for package
> authors to change how syntax highlighting is performed in major modes?

Sorry, I don't think I really understand what is the complaint/issue
you are raising here, and what solution would you like to suggest for
those issues.  Could you perhaps elaborate?  A specific example where
the current code doesn't work would be a good starting point.

Thanks.





  parent reply	other threads:[~2016-05-10 15:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10  3:12 bug#23501: Non-regex-based syntax highlighting Nir Friedman
2016-05-10 15:57 ` Richard Stallman
2016-05-10 15:59 ` Eli Zaretskii [this message]
2016-05-10 18:55   ` Nir Friedman
2016-05-10 19:21     ` Eli Zaretskii
2016-05-10 20:16       ` Nir Friedman
2016-05-11  7:49         ` Eli Zaretskii
2020-08-12  2:31           ` Stefan Kangas
2016-05-11 17:56         ` John Mastro

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=834ma5dhut.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23501@debbugs.gnu.org \
    --cc=quicknir@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.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).