This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-05
Channels
- # announcements (3)
- # beginners (225)
- # calva (3)
- # cider (110)
- # circleci (18)
- # clj-kondo (15)
- # cljdoc (1)
- # cljsrn (12)
- # clojure (77)
- # clojure-dev (39)
- # clojure-europe (3)
- # clojure-houston (2)
- # clojure-italy (9)
- # clojure-nl (16)
- # clojure-romania (1)
- # clojure-spec (5)
- # clojure-uk (20)
- # clojuredesign-podcast (28)
- # clojurescript (89)
- # core-async (4)
- # cursive (10)
- # datomic (3)
- # defnpodcast (5)
- # emacs (17)
- # events (1)
- # figwheel (4)
- # graalvm (6)
- # juxt (1)
- # pathom (4)
- # pedestal (5)
- # re-frame (4)
- # remote-jobs (3)
- # rewrite-clj (4)
- # shadow-cljs (90)
- # spacemacs (2)
- # sql (7)
- # tools-deps (4)
- # vim (52)
- # xtdb (7)
Is there a tool can help me find typos when developing clojure in emacs? especially for typo :keyword
.
@doglooksgood This approach might work https://metaredux.com/posts/2019/05/24/eradicate-typos-in-source-code.html
Looks like misspell does a good job for english words. But in my case, there are a lot variables that is not english. I hope something find the similar words those has posibility for one of them is typo. e.g. params and parmas
are you genuinely aiming to tackle typos? i.e. literally the generalised problem of typos, be it in docstrings, variable names, etc
rather, you might want a two-faced solution which really isn't typo-centric:
- using clojure.spec
to catch bad arguments
- using a specific keyword linter for ensuring consistency between the corpus of keywords within your codebase
It is called keyword-typos
: https://github.com/jonase/eastwood#keyword-typos
It is disabled by default because on several Clojure projects I have run it on, it can be fairly noisy, for code written apparently as the author intended it, e.g. some Clojure authors intentionally use keywords that are similar to each other.
with this approach, you trim down the problem domain and can forget about English language intricacies, an approach which seems bound to give false positives/negatives.
@vemv Often people just repeat the same typo all over the code. clojure.spec
wonโt help you with that. ๐
I do not do copy/paste so much in order to find typos. But how I find it is running into some error. compiler won't tell you the keyword is wrong and keyword is so widely used in Clojure.
anybody has a good example of how to setup emacs/cider/shadow-cljs properly? I'm not able to get repl working in emacs
have you considering going with a starter/defaults kit for a while? e.g. https://github.com/bbatsov/prelude later you can discard it, the point is to get you up and running