This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-05
Channels
- # admin-announcements (3)
- # architecture (1)
- # beginners (16)
- # boot (14)
- # cljsrn (205)
- # clojars (4)
- # clojure (100)
- # clojure-austin (2)
- # clojure-india (1)
- # clojure-poland (7)
- # clojure-russia (95)
- # clojure-spec (25)
- # clojure-uk (127)
- # clojurescript (32)
- # core-async (7)
- # cursive (2)
- # datascript (4)
- # datomic (3)
- # editors-rus (1)
- # emacs (8)
- # events (10)
- # funcool (5)
- # gorilla (2)
- # hoplon (6)
- # jobs (1)
- # lein-figwheel (7)
- # leiningen (2)
- # luminus (11)
- # om (7)
- # onyx (119)
- # other-languages (31)
- # proto-repl (1)
- # proton (37)
- # protorepl (3)
- # re-frame (60)
- # reagent (8)
- # spacemacs (9)
- # specter (21)
- # spirituality-ethics (2)
- # yada (10)
anyone else have a problem with emacs where it just stops responding to emacsclient? emacs still works but trying to connect to the frame with emacsclient just hangs until it’s canceled
I’m at a loss here because it doesn’t happen often but the only recourse is to restart emacs. I’m not even sure how phrase this question to google
if I try to run a term instance in these cases it opens and then shuts almost immediately
I have only ever run into that problem when I evaluate something in Cider that causes Emacs to lock up.
I got a similar problem when I upgraded to “El Capitan”, the problem was that the system were using the default emacsclient that OSX provides that is way-way-way older than my emacs and I was not able to connect, and after each system update it seems like my aliases and emacsclient are replaced by the default OSX