You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if it would be difficult to add verilog-mode specific faces so that I could have different color/theme for those buffers. I see there's a few of these for verilog only things like p1800 keywords but most, like comment face, always use the standard comment face. I looked at verilog-mode.el but the face stuff is a bit beyond my understanding. If you could give me a simple example of one, e.g. verilog-mode-comment-face, I could extend it to the other faces.
I could just use this locally or submit it for the main trunk if you like. I'd think they would all default to just inheriting the common version of the face so that they work like they do now if not customized.
Thanks,
David
The text was updated successfully, but these errors were encountered:
To determine how to get the right face settings, in a verilog buffer, use M-x customize then Faces then whatever. Change it to what you want, then at top "apply and save". This will make a global change. Now go to your ~/.emacs or rc/.emacs and find something like this
Author Name: David Rogoff
Original Redmine Issue: 1323 from https://www.veripool.org
Hi.
I was wondering if it would be difficult to add verilog-mode specific faces so that I could have different color/theme for those buffers. I see there's a few of these for verilog only things like p1800 keywords but most, like comment face, always use the standard comment face. I looked at verilog-mode.el but the face stuff is a bit beyond my understanding. If you could give me a simple example of one, e.g. verilog-mode-comment-face, I could extend it to the other faces.
I could just use this locally or submit it for the main trunk if you like. I'd think they would all default to just inheriting the common version of the face so that they work like they do now if not customized.
Thanks,
David
The text was updated successfully, but these errors were encountered: