-
Notifications
You must be signed in to change notification settings - Fork 23
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
Default to cc-mode-get-declarations
#97
Conversation
From my experiments everything seems fine, but more testing would be appreciated! |
2463103
to
e270cc5
Compare
This is a preparation before the next commit where that part will no longer be c-mode specific.
e270cc5
to
9e4d1cc
Compare
It isn't actually specific to cc-mode, and works in a way similar to the previous default `scan-identifiers`, except that because it only goes through places with properties set, it is: 1. more performant due to less motion 2. less likely to introduce wrong coloring as in ankurdave#40 or ankurdave#62 We also rename the function to remove infix `cc-mode` as it isn't (and never really have been) specific to c-mode. Fixes: ankurdave#94
FTR: after this PR is merged, I think further simplifications to I'll refrain from doing that as part of this PR though because that would change the way |
Done. After further research I figured it may be skipped with minimal changes to the motion. Tested with As a side note, I realized |
afa6468
to
9393a14
Compare
UPD: further simplification to last commit: I just realized that |
e6226ee
to
3a9e24a
Compare
So, let's merge this and #98 I think. I have used them for a day with C/Meson/Python, no problems, everything seems fine. |
It isn't actually specific to cc-mode, and works in a way similar to the previous default
scan-identifiers
, except that because it only goes through places with properties set, it is:We also rename the function to remove infix
cc-mode
as it isn't (and never really have been) specific to c-mode.Fixes: #94