This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # 100-days-of-code (13)
- # announcements (3)
- # beginners (122)
- # boot (17)
- # calva (19)
- # cider (27)
- # cljdoc (3)
- # cljs-dev (1)
- # clojure (138)
- # clojure-dev (5)
- # clojure-italy (5)
- # clojure-nl (20)
- # clojure-russia (3)
- # clojure-spec (14)
- # clojure-uk (119)
- # clojurescript (45)
- # core-async (2)
- # datomic (23)
- # editors (28)
- # emacs (35)
- # figwheel (2)
- # fulcro (26)
- # graphql (2)
- # hyperfiddle (11)
- # jobs (4)
- # luminus (5)
- # mount (2)
- # off-topic (52)
- # onyx (39)
- # reagent (86)
- # ring-swagger (2)
- # spacemacs (20)
- # tools-deps (9)
- # yada (4)
I am having issues installing spacemacs. I get
File is missing: Cannot open load file, No such file or directory, bind-map
In the installation message buffer I get
Package ws-butler is unvailable. Is the package name misspelled?
@mario.cordova.862 are you still running with
There is also a setting in
.spacemacs to us only http to connect to melpa.
If ws-butler is an install from Github rather than an elpa install, there may be something broken with your git install or git needs to be configured to work with a proxy (assuming you are installing Spacemacs in a network behind a proxy)
emacs --insecure and it pulled all the packages and afterwards I was able to start emacs regularly without the
@mario.cordova.862 the setting
dotspacemacs-elpa-https t in
dotspacemacs/init section of
.spacemacs gives you the same results as
emacs --insecure once Spacemacs is installed.
@mario.cordova.862 yes, but it just means you are downloading packages from elpa over http rather than https. Otherwise it makes no difference to the rest of emacs.
I see well its working just fine so will leave it as it but will keep this in mind just in case it appears again.
Or it could be just a broken download of the elpa package, in which case you should check under the
.emacs.d/elpa directory (in the relevant sub directories for Emacs version and Spacemacs branch) and delete the relevant package. Restart Emacs and it will try and download the package again.
@plexus thanks. I though I spotted a whitespace bug, but just me reading the diff incorrectly, sorry.
The CircleCI tests are failing where you have a space between the org-mode header and the content in the http://readme.org. Seems a bit picky, but easily fixed.
@plexus a matter of style perhaps, but I put additonal layer config under the :variable name
Just wondering if this is my convention or if everyone does it this way. I think most of examples I've seen are like this.
(clojure :variables clojure-enable-sayid t clojure-enable-clj-refactor t)