Do you have bandwidth to work on integrating this? Ideally I'd like to see the following steps taken: I also never knew the vs trick, so that's good to know - thanks! When I look at the raw file on github, it honestly doesn't look too bad, but I suspect that my browser is smarter about tabs than my default emacs configuration. verilog-mode.el has quite a few tabs in it, so I am probably to blame for some of the funky indentation. I'm a card-carrying member of the 'tabs are evil' brotherhood (and to treat them like 2 spaces so lines don't get too long). I use a custom but just for the git folder I have created files that sets to the default value of Redmine Comment These comments (there are many other instances of similar single comments) be prefixed with instead of Add a file with the relevant variables set so that the formatting stays consistent. When the match isĮxtended, its starting position is allowed to occur beforeĪs a general recommendation, try to avoid using `looking-back' Possible, stopping when a single additional previous characterĬannot be part of a match for REGEXP. If GREEDY is non-nil, extend the match backwards as far as Starting position, to avoid checking matches that would start LIMIT if non-nil speeds up the search by specifying a minimum Like `looking-at' except matches before point, and is slower. "Return non-nil if text before point matches regular expression REGEXP. (defun verilog-looking-back (regexp limit &optional greedy)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |