Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Highlighting bug; highlights wrong block of code #1092

Open
veripoolbot opened this issue Sep 21, 2016 · 2 comments
Open

Highlighting bug; highlights wrong block of code #1092

veripoolbot opened this issue Sep 21, 2016 · 2 comments

Comments

@veripoolbot
Copy link
Collaborator


Author Name: Kaushal Modi
Original Redmine Issue: 1092 from https://www.veripool.org


Hello,

Lately (in about last month), I have been seeing an odd highlighting issue most likely related to @verilog-mode@. It can be best described with the help of the below gifv animation:

"GIFV":http://i.imgur.com/yXLBoLO.gifv

I have posted the same issue on the emacs-devel mailing too: https://lists.gnu.org/archive/html/emacs-devel/2016-09/msg00590.html

I cannot tell if the issue is with:

  • emacs 25.x
  • verilog-mode
  • Use of something new in the verilog code that is false-triggering that highlight.. it looks like the highlight for @verilog-highlight-includes@. But I need to yet confirm that.. I am waiting for that exact highlighting bug to get triggered (as it seems to happen randomly).

A possibly related issue ( https://lists.gnu.org/archive/html/emacs-devel/2016-09/msg00597.html ) reported in the same thread is that the valid @verilog-highlight-includes@ highlights are duplicating on the same region multiple times with each @M-X revert-buffer@.

Please refer to the above link for more info.

@veripoolbot
Copy link
Collaborator Author


Original Redmine Comment
Author Name: Kaushal Modi
Original Date: 2016-09-21T14:50:41Z


The same links.. now hyperlinked:

@veripoolbot
Copy link
Collaborator Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2017-11-19T13:35:48Z


AFAIK still a problem, perhaps someone would like to contribute a patch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant