This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-09
Channels
- # adventofcode (1)
- # aleph (2)
- # beginners (28)
- # boot (26)
- # boot-dev (8)
- # cider (10)
- # clara (10)
- # cljs-dev (130)
- # cljs-experience (1)
- # cljsrn (12)
- # clojure (118)
- # clojure-austin (40)
- # clojure-boston (1)
- # clojure-chicago (1)
- # clojure-dusseldorf (1)
- # clojure-estonia (11)
- # clojure-france (1)
- # clojure-greece (3)
- # clojure-italy (19)
- # clojure-nl (1)
- # clojure-russia (1)
- # clojure-spec (19)
- # clojure-uk (34)
- # clojurescript (62)
- # core-logic (7)
- # cursive (11)
- # datomic (35)
- # emacs (15)
- # fulcro (264)
- # jobs (4)
- # leiningen (5)
- # midje (4)
- # off-topic (74)
- # onyx (27)
- # planck (14)
- # protorepl (4)
- # re-frame (37)
- # reagent (62)
- # rum (2)
- # shadow-cljs (171)
- # slack-help (5)
- # spacemacs (6)
- # specter (9)
I know about set-window-dedicated-p. It's not what . Iwant: I want a situation where a frame is attached to a wincow and does NOT displ.ay any other windows
Even with set-window-dedicated-p, I get the situation taht the frame may decide to split and display two windows. I don't want that. I want this frame to display this one window -- and never display anything else.
basically I want a command that says: this frame has this current layout with these windows/buffers; NEVER change at all; force all new windows/buffers to appears elsewhere
https://www.gnu.org/software/emacs/manual/html_node/eintr/what_002dline.html is this for real? in emacs, getting "what line am I currently on" requires scanning through the entire buffer ?
-- the 'persistent action' seems to do basically that. although it'd be more uniform if I could use a plain action
I'm trying to debug an issue where shutdown hooks are not run when I do cider-restart
; I'm having trouble even finding the code that kills the server. any tips?
(defun cider--close-connection-buffer (conn-buffer)
"Close CONN-BUFFER, removing it from variable `cider-connections'.
Also close associated REPL and server buffers."
(let ((buffer (get-buffer conn-buffer))
(nrepl-messages-buffer (and nrepl-log-messages
(nrepl-messages-buffer conn-buffer))))
(setq cider-connections
(delq buffer cider-connections))
(when (buffer-live-p buffer)
(with-current-buffer buffer
(when spinner-current (spinner-stop))
(when nrepl-tunnel-buffer
(cider--close-buffer nrepl-tunnel-buffer)))
;; If this is the only (or last) REPL connected to its server, the
;; kill-process hook will kill the server.
(cider--close-buffer buffer)
(when nrepl-messages-buffer
(kill-buffer nrepl-messages-buffer)))))
if I do cider-jack-in
followed by cider-restart
, my assumption is that the jvm running the nrepl server gets shutdown
is the process managed by emacs, and so kill-buffer
ends up killing the process?
I can contrast this effect with what happens when I do lein trampoline repl :headless
(probably also lein repl
would be equivalent) followed by C-c
, in which case the shutdown hooks do run