Making ns-qualified keywords not have font-lock-type-face #468
Comments
In case it helps, this is the culprit:
|
@Bost I think your ns font-locking changes addressed this, right? |
Yes it does. (@vemv Bozo references to the 14d4221.) user> ::kws.grid/column-settings
RuntimeException Invalid token: ::kws.grid/column-settings clojure.lang.Util.runtimeException (Util.java:221)
user> :kws.grid/column-settings
:kws.grid/column-settings
user> (namespace :kws.grid/column-settings) ;; namespace font-locked as font-lock-type-face
kws.grid
user> (name :kws.grid/column-settings) ;; keyword names font-locked as clojure-keyword-face
column-settings
user> And here is how is looks like: So to answer:
Yea you were looking at a buggy feature implementation, now hopefully fixed. Please get the 14d4221 and have a look again. |
For the record: it is - if you Will checkout CIDER @ latest asap. Thanks! |
What??? Egh... user> (require '[clojure.core :as kws.grid])
nil
user> ::kws.grid/fn
:clojure.core/fn
user> ::kws.grid/ufo
:clojure.core/ufo
user> (namespace ::kws.grid/ufo) ;; I wonder how many folks get confused over this?
clojure.core
user> (name ::kws.grid/ufo)
ufo
user> (name :kws.grid/ufo)
ufo
user> (namespace :kws.grid/ufo)
kws.grid
user> egh... really. I think it would be a good idea to indicate it with some different font-face. @bbatsov? |
One normally aliases using close terms (e.g clojure -> clj) Thus, So a different font-fact may be overkill. |
autogenerated with https://github.com/MalloZup/doghub: issue inactive since 450 days. Please update the issue or close it |
Given a ns-qualified keyword such as:
::kws.grid/column-settings
I'd like only
clojure-keyword-face
to be applied to it. But alsofont-lock-type-face
is partially applied to it:How it looks like
How it is parsed
The problematic bit seems to be
(font-lock-type-face clojure-keyword-face)
.I'm not sure if this is a feature. To me it looks buggy, because only
grid
gets the grey coloring. But in the examplegrid
does not have a special meaning.Using clojure-mode latest/pristine, no fork
The text was updated successfully, but these errors were encountered: