This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-25
Channels
- # aws (2)
- # bangalore-clj (2)
- # beginners (90)
- # boot (89)
- # bristol-clojurians (1)
- # cider (23)
- # cljs-dev (48)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (118)
- # clojure-argentina (3)
- # clojure-austin (8)
- # clojure-czech (1)
- # clojure-dev (18)
- # clojure-ireland (1)
- # clojure-italy (4)
- # clojure-russia (6)
- # clojure-spec (75)
- # clojure-uk (224)
- # clojurescript (103)
- # core-async (28)
- # cursive (3)
- # datascript (7)
- # datomic (15)
- # dirac (30)
- # emacs (14)
- # events (3)
- # figwheel (1)
- # hispano (1)
- # hoplon (176)
- # lambdaisland (1)
- # lein-figwheel (6)
- # off-topic (21)
- # om (7)
- # onyx (2)
- # pedestal (6)
- # re-frame (4)
- # reagent (15)
- # spacemacs (67)
- # specter (13)
- # testing (9)
- # untangled (65)
- # vim (6)
- # yada (1)
@richiardiandrea @qqq inf-clojure
works perfectly with boot 👌
Are any Emacs people coming to ClojureD? We're having an Emacs Berlin meetup a few days before, and we're thinking of making it a Clojure-themed one
It would be super awesome if we could have one or more talks on CIDER/clj-refactor/clojure-mode/inf-clojure/parinfer/...
It'll be Wednesday 22 February, so three days before ClojureD. We could make it an early pre-event for people already in town. Lambda Island is happy to sponsor some pizzas 😉
oi @plexus I would love to but can’t make clojureD this year unfortunately… however i may be in berlin on 16th-17th Feb
@plexus I'm planning on travelling with a friend from Zurich to ClojureD and would love to go to the Emacs meetup. Three days earlier is a lot too early, unfortunately.
that's understandable, some people might not mind spending a few days in Berlin though. The meetup is always the last Wednesday of the month.
I'll try to remember in case I might find myself stranded in Berlin on the forth week of a month^^
where instead of kill-buffer, kill-9-buffer does not ask for any confirmation and executes with extreme prejuditce ?
@qqq In the docs for kill-buffer
it says....
The functions in ‘kill-buffer-query-functions’ are called with the
buffer to be killed as the current buffer. If any of them returns nil,
the buffer is not killed. The hook ‘kill-buffer-hook’ is run before the
buffer is actually killed. The buffer being killed will be current
while the hook is running. Functions called by any of these hooks are
supposed to not change the current buffer.
Perhaps you could temporarily override kill-buffer-query-functions
with an empty list. (Just a guess. I have not tried it myself.)