This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-09
Channels
- # beginners (55)
- # boot (173)
- # clara (3)
- # cljs-dev (10)
- # cljsjs (3)
- # clojars (11)
- # clojure (110)
- # clojure-austin (5)
- # clojure-berlin (13)
- # clojure-chicago (2)
- # clojure-dusseldorf (3)
- # clojure-france (24)
- # clojure-italy (4)
- # clojure-portugal (1)
- # clojure-russia (60)
- # clojure-serbia (8)
- # clojure-spec (150)
- # clojure-uk (129)
- # clojurescript (87)
- # core-logic (1)
- # cursive (75)
- # datavis (1)
- # datomic (75)
- # devcards (4)
- # dirac (17)
- # emacs (50)
- # events (2)
- # hoplon (9)
- # jobs (4)
- # jobs-discuss (37)
- # lein-figwheel (3)
- # luminus (5)
- # off-topic (54)
- # om (9)
- # om-next (5)
- # onyx (10)
- # perun (11)
- # protorepl (11)
- # quil (2)
- # rdf (2)
- # re-frame (14)
- # reagent (58)
- # ring (13)
- # ring-swagger (10)
- # rum (52)
- # spacemacs (8)
- # test-check (10)
- # untangled (17)
- # yada (34)
when using cider, sometime M-x cider-connect RET <my-host> RET, It will prompt for input password.
I've only seen the prompts for the host and the port. Is it asking for the password to an SSH key or something?
If I use lein repl :connect <host>:<port>
, it will works. I don't think it need password. the cider-connect use ssh instead of direct connect to the nrepl server?
@qqq looks like there’s almost feature-parity indeed, but with more vim-like bindings I guess. If I’d start fresh today, I would defiantly give it a shot
@qqq @hkjels I’d put in a word for lispy, which is not exactly evil+paredit, but paredit if it was designed to be modal (in a different way from evil, but orthogonal enough that they can easily work together). If vi is a language for editing text, I think of lispy as a DSL for editing lisps. It’s easier to understand as you use it, but to me it is the tree editor that was promised.
@sooheon : lispy, is that the one where certain keys have special meaning if you're right before a ( or right after a ) ?
the idea being, you never want to type j( or k(, so if you're right in front of a (, and you type j or k, interpret it special ?
Yep that’s it. It has intuitive keys for navigating across those |( or )| points, and editing.
It works well with evil because I
and A
in normal mode can take you to |( or )| very easily
here's something I could never get it to work with lispy (and I spent a good two days configuring it)
I think that prev/next line is a less useful way to think of it than parent/sibling, which hjkl navigate
alot of the time the issue is: 1) I'm looking at a place on my screen (not where my cursor is) 2) I want to move my cursor there 3) hjkl makes sense, but thikning of "parent/nesting" not so much
Fair enough. In that case, q
a
-
should help. I think a lot of the rest of the time, you’re thinking “I want to move up in this if expression” or “I want to go to the other clause”
Anyways, if you’re interested, the demos do a better job of selling than I could just yapping :)
so a number of things that I find confusing about h/l suppose I Have:
(let [a1 ...
a2 ...]
(b1 ...)
(b2 ...)
(b3 ...))
a very common thing I want to do is place cursor on a1, then move down to a2, then move down to b1, then b2, then b3 /// and if I try to move with forward/backward sexp, I have to get on the right sexp, then I have to hit l which is weird when my brain says "dude, we want to move to next line"If after selecting a2, (i.e. it’s marked), I decide not to edit it, and I want to get to b1, I’d probably do hmj
you know what you could do to really convince me and would also convince lots of other people?
write a elisp module, which does the following: it records the sequence of the last 20 evil/paredit commands I'm editing; then it finds subsequences that can be optimized, and say "dude, this took you 15 strokes; in lispy, the following 4 strokes are equiv"
if it could look at my edits, get a diff, and compute the optimal lispy solution, I'd learn lispy faster and also realize it's full power
But yes, that’s a great idea which if I can’t do I’ll try to persuade the package author to try :)