-
-
Notifications
You must be signed in to change notification settings - Fork 247
Fix namespace font locking #448
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
Conversation
[CamelCase])) | ||
|
||
;; examples of valid namespace definitions | ||
(comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd actually also add new unit tests verifying the validity of your changes.
CHANGELOG.md
Outdated
@@ -9,6 +9,7 @@ | |||
* [#443](https://github.com/clojure-emacs/clojure-mode/issues/443): Fix behavior of `clojure-forward-logical-sexp` and `clojure-backward-logical-sexp` with conditional macros. | |||
* [#429](https://github.com/clojure-emacs/clojure-mode/issues/429): Fix a bug causing last occurrence of expression sometimes is not replaced when using `move-to-let`. | |||
* [#423](https://github.com/clojure-emacs/clojure-mode/issues/423): Make `clojure-match-next-def` more robust against zero-arity def-like forms. | |||
* Fix namespace font-locking |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can also mention here the GH issue you've fixed. This sentence should end with a .
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did the fix out of pure excitement of having found "a pristine spot on a wall I can spray my tag on". Ok seriously there is no GH issue for my PR. Although the #280 seems to be closely related.
Hmm, that's odd. There shouldn't be any failing tests (there were certainly none last time I checked). Unfortunately the TravisCI setup seems to have been magically broken and I don't have time to look into this myself at this time. |
It seems like something's messed up somewhere also on my side. Here the
|
I'm closing this PR. I'm gonna send you a new PR without regressions. |
The commits are consistent with our [contribution guidelines][1]
You've added tests (if possible) to cover your change(s). Indentation & font-lock tests are extremely important!
All tests are passing (
make test
)Using cask for testing is a pain :-(
However
M-x spacemacs/ert-run-tests-buffer
shows no new errors (on top of those 8 existing already)M-x checkdoc
warnings