This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-08
Channels
- # announcements (2)
- # aws (1)
- # beginners (134)
- # calva (26)
- # cider (48)
- # cljdoc (41)
- # cljs-dev (12)
- # clojure (178)
- # clojure-brasil (1)
- # clojure-europe (16)
- # clojure-italy (30)
- # clojure-nl (13)
- # clojure-spec (118)
- # clojure-uk (81)
- # clojurescript (209)
- # community-development (77)
- # cursive (7)
- # datomic (23)
- # duct (6)
- # emacs (15)
- # events (2)
- # figwheel (13)
- # figwheel-main (18)
- # fulcro (4)
- # jackdaw (4)
- # jobs (6)
- # jobs-discuss (6)
- # kaocha (2)
- # lein-figwheel (3)
- # off-topic (4)
- # other-languages (22)
- # pathom (2)
- # pedestal (9)
- # perun (10)
- # portkey (1)
- # re-frame (41)
- # reagent (6)
- # reitit (4)
- # remote-jobs (1)
- # ring-swagger (6)
- # rum (5)
- # shadow-cljs (300)
- # sql (3)
- # test-check (6)
- # testing (7)
- # vim (1)
- # yada (9)
These kind of errors are locking up my emacs frequently:
CompilerException clojure.lang.ExceptionInfo: Call to clojure.core/ns did not conform to spec:
In: [1] val: ((require [clojure.set :as set]) (:gen-class)) fails spec: :clojure.core.specs.alpha/ns-form at: [:args] predicate: (cat :docstring (? string?) :attr-map (? map?) :clauses :clojure.core.specs.alpha/ns-clauses), Extra input
#:clojure.spec.alpha{:problems [{:path [:args], :reason "Extra input", :pred (clojure.spec.alpha/cat :docstring (clojure.spec.alpha/? clojure.core/string?) :attr-map (clojure.spec.alpha/? clojure.core/map?) :clauses :clojure.core.specs.alpha/ns-clauses), :val ((require [clojure.set :as set]) (:gen-class)), :via [:clojure.core.specs.alpha/ns-form], :in [1]}], :spec #object[clojure.spec.alpha$regex_spec_impl$reify__2436 0x1fdf1c5 "clojure.spec.alpha$regex_spec_impl$reify__2436@1fdf1c5"], :value (pegthing.core (require [clojure.set :as set]) (:gen-class)), :args (pegthing.core (require [clojure.set :as set]) (:gen-class))}, compiling:(/home/chaselambert/projects/brave-book/pegthing/src/pegthing/core.clj:1:1)
pegthing.core>
I hate to keep coming here and bugging you folks. Just wondering if it's something fixable I should be doing or something I can help (filing an issue in the appropriate place, etc) for other users
try turning on the profiler? M-x profiler-start
, do something to lock it up and then m-x profiler-report
after a few seconds of lockup
I'm not even clear on why exactly that would even create an error. it's the first step of a much used tutorial but that's for a different day i guess
interesting. maybe this is old? From brave and true. https://github.com/flyingmachine/pegthing/blob/master/src/pegthing/core.clj
I did the profiler-start things. Hopefully I can report back with more info if I lock up again. I haven't been able to use m-x after the lock up though. Are you saying it will save the info for when I restart?
just locked on me again. on restart I'm being told profiler-report
is not a valid command name
I can't even force kill emacs specifically, i have to shut down my whole linux instance but that might just be my weird system.
i've already been debating trying to find a way to get emacs 26 on debian. not sure if possible.
from what I gathered, debian doesn't care about such things right. 26 isn't available on the debian repositories unless i'm mistaken
correct. debian cares about years long stability. i understand debian makes a great application server and a frustrating dev machine
ahhh. the irony is in this case, stability means instability? But this could be some user error on my part
i have to run on debian though so let me explore workarounds. maybe build from source? I'm just using phrases though, not entirely clear on that. I'll leave #cider alone though
Building emacs from source in the linux world is pretty easy and straight forward
And now I'm proud to say I've built emacs from source! I guess I've done skipped from 25.1.1 to 27.0.50. I count this as a big +1 in my tech/hacking skills! Thanks again for all the help these last couple of weeks @U11BV7MTK. Fingers crossed I can leave you alone for a bit.
Congrats! 🙂 Hopefully that helps solve your issues.
worth noting: elisp files get compiled into elc files (c is compiled). Worth deleting these when starting up with emacs 27
They’re compiled versions of the elisp files, which emacs makes automatically, and may mess with your newer version of emacs.
Which only matters now, when jumping from 25->27, or if some change in an elisp file wasn’t being picked up. Aka, you don’t have to worry about it normally.
ahh, thanks for the clarification. I did this all on a brand new fresh install because I'm just weird like that. can't find any .elc files so I think I'm good to go
until you just realized you erased a couple of learning files with lots of commented notes. d'oh!
Debian testing has Emacs version 26.1 available, so you could just upgraded. It would take less time than compiling Emacs (depending on CPU speed Vs internet speed). I always used to used the testing version of Debian as it was always pretty stable (at least between 1995 and 2005)