This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-02
Channels
- # aws-lambda (1)
- # beginners (28)
- # boot (54)
- # cider (11)
- # clara (28)
- # cljs-dev (74)
- # cljsrn (13)
- # clojure (342)
- # clojure-austin (3)
- # clojure-dusseldorf (4)
- # clojure-france (2)
- # clojure-greece (11)
- # clojure-italy (42)
- # clojure-poland (7)
- # clojure-russia (11)
- # clojure-spec (44)
- # clojure-uk (156)
- # clojure-ukraine (4)
- # clojurescript (102)
- # cursive (17)
- # datascript (19)
- # datomic (17)
- # dirac (39)
- # emacs (22)
- # funcool (56)
- # hoplon (25)
- # jobs (3)
- # jobs-discuss (31)
- # leiningen (2)
- # luminus (4)
- # lumo (3)
- # off-topic (47)
- # om (51)
- # onyx (57)
- # re-frame (13)
- # reagent (57)
- # remote-jobs (15)
- # ring (9)
- # ring-swagger (7)
- # robots (2)
- # rum (6)
- # specter (16)
- # sql (7)
- # test-check (37)
- # untangled (7)
- # yada (5)
I have an rsync command which rsyncs a LOCAL DIR to a REMOTE-DIR now, whenver I save a file in LOCALDIR, I want this rsync command to run
you can use dirwatch or similar along with rsync
yeah that seems fair
only works on linux though
I now have this weird problem: when I'm ssh-ed into a remote machine (via eshell/tramp), it can't find boot 😞
after firing up a eshell, how do I send commands to taht eshell? (let ((default-directory ...)) (eshell)) is caushing problems for me
so now I want to do
(eshell)
(exec-cd in eshell)
but eshell-command apparently deosn't do thatit seems that whem I'm using cd /ssh:username@host:/... all my path / env are broken, reflecting the host machine, not the remote machine
@qqq https://www.gnu.org/software/emacs/manual/html_node/elisp/Signals-to-Processes.html
so the solution turned out to be (1) set buffer of process to nil, and (2) then kill the process
Symptom: 1) I have a Org Special Edit buffer. 2) When I try to kill the buffer, I get a "wrong type argument: stringp, nil" -- and I CAN"T KILL THE BUFFER. How to reproduce this: 1) Open a file in buffer X 2) Enter a org-special-edit of a source code block of X (call this new buffer Y) 3) switch to buffer X 4) kill buffer X 5) now, try to kill buffer Y ==> error of "Wrong type argument: stringp, nil" Somehow, if I kill the "root/parent" org-buffer, then I can no longer delete the org-special-edit "child" buffer
okay, got it working, it was kill-buffer-hook that was preventing the buffer from being killed