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

Indenting/Highlighting user defined types #308

Open
veripoolbot opened this issue Dec 16, 2010 · 2 comments
Open

Indenting/Highlighting user defined types #308

veripoolbot opened this issue Dec 16, 2010 · 2 comments
Labels

Comments

@veripoolbot
Copy link
Collaborator

@veripoolbot veripoolbot commented Dec 16, 2010


Author Name: Jonathan Greenlaw
Original Redmine Issue: 308 from https://www.veripool.org
Original Date: 2010-12-16


Indenting and highlighting does not recognize user defined types as specified by the verilog-typedef-regexp variable.

@veripoolbot
Copy link
Collaborator Author

@veripoolbot veripoolbot commented Dec 16, 2010


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2010-12-16T18:40:38Z


Thanks for filing.

@veripoolbot
Copy link
Collaborator Author

@veripoolbot veripoolbot commented Feb 21, 2011


Original Redmine Comment
Author Name: Michael McNamara
Original Date: 2011-02-21T02:21:40Z


Hmm, this is way difficult. I like Wilson's idea of using verilog-typedef-regexp as the single way to tell emacs how to indent as well; but the problem is verilog-typedef-regexp is defined to match just a subset of the type, as for example if I use _t as a subscript for my types, as in:
typedef reg[31:0] word_t;
typedef reg[7:0] byte_t;

then I would (setq verilog-typedef-regexp "_t$")

Better for the indent part would be if I did (setq verilog-typedef-regexp "\sw+_t$")
I.E. something that would match the entire "word_t" instead of just the "_t" part

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

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.