This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-20
Channels
- # bangalore-clj (1)
- # beginners (145)
- # boot (8)
- # braid-chat (2)
- # capetown (2)
- # cider (27)
- # cljs-dev (232)
- # cljsrn (30)
- # clojure (223)
- # clojure-boston (1)
- # clojure-dusseldorf (2)
- # clojure-greece (1)
- # clojure-italy (21)
- # clojure-russia (16)
- # clojure-sanfrancisco (13)
- # clojure-spec (33)
- # clojure-uk (56)
- # clojurescript (165)
- # core-async (16)
- # core-logic (5)
- # cursive (14)
- # data-science (2)
- # datavis (2)
- # datomic (49)
- # duct (15)
- # editors (5)
- # emacs (6)
- # fulcro (11)
- # graphql (11)
- # hoplon (8)
- # jobs (4)
- # jobs-discuss (82)
- # jobs-rus (7)
- # leiningen (4)
- # luminus (5)
- # off-topic (90)
- # om (7)
- # om-next (1)
- # parinfer (67)
- # pedestal (34)
- # portkey (46)
- # re-frame (12)
- # reagent (4)
- # reitit (3)
- # remote-jobs (1)
- # ring-swagger (8)
- # shadow-cljs (13)
- # spacemacs (18)
- # specter (6)
- # sql (5)
- # tools-deps (4)
- # unrepl (40)
- # yada (26)
I think someone's not too long ago was curious: "what so nice and unique about eshell" https://twitter.com/iLemming/status/975889923571003393
Did you try removing ~/.emacs.d
completely and run spacemacs installation from beginning?
sometimes emacs gets confused about which packages it has installed and then freaks out
@achikin from time to time I run git clean -Xdf
in ~/.emacs.d
and let it install and recompile all the packages. Most of the time it doesn't hurt. I had a few times a problem with that, that turned out to be thing in my config (I would change something in one of my own layers, that doesn't affect anything unless I get to a clean slate). Sometimes it is hard to track down problem such that. In that case I would disable all the layers, and then start adding them one-by-one, until I find the one that causes the error.
@ag thank you. Finally I did sonething like this - removed emacs.d, removed all configs and reinstalled from scratch
yeah, it's a bit drastic... git clean
cool though. Try running it with -n
key, that way it will do "dry run": and will not actually delete things, but shows you what would be deleted
@jr0cket I hope you don't mind minimal PRs, i found small errors in the key combos for changing line numbering while reading along.
Comments and PRs are most welcome. Thank you.
Your PR merged, thanks again