Clojurians
#editors
<
2016-03-08
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

jasongilman01:03:59

I just created a gist describing my Atom setup. I thought I'd mention it here. https://gist.github.com/jasongilman/d1f70507bed021b48625#file-my_atom_clojure_setup-md

nkraft15:03:39

Anyone using MacVim and Fireplace for Clojure? I usually use emacs for development, but I've been playing with Vim and Fireplace too. Fireplace seems to have a problem, though: I can connect to my repl without problems, and the formatting commands all work, but when I try cqc or cqp I get "not an editor command".

nkraft15:03:50

Is this a MacVim thing, or am I doing something wrong?

snoe15:03:14

@nkraft: cqc and cqp are normal mode mappings not commands. (So not on the : prompt).

nkraft16:03:31

Thanks @snoe. Still getting used to Vim for Clojure. I use it a lot for bash scripts, but that's been about it.

snoe16:03:51

np, if you look up at @dominicm message he has a pretty good run down of some of the things you can do with vim and clojure.

dominicm17:03:57

I should push up my files and do a video

dominicm17:03:13

I've got some really nice stuff lately.

dominicm17:03:45

As in, since I started my job I've been forced to optimise.

dominicm17:03:29

I want to put together a motion for doing clojure comments over a range

dominicm17:03:42

I think that would be super cool

dominicm17:03:52

Not a motion, a, action?

nkraft18:03:13

@dominicm: That was a great list you put above, got me started with Vim and Clojure. Love to see more of your thoughts on the subject.

dominicm18:03:24

@nkraft I'll try. I'm pretty new to doing advanced stuff.

nkraft18:03:00

@dominicm: So am I, though you're ahead of me in the vim+clojure world. :simple_smile:

dominicm18:03:39

@nkraft: Ah, so you're not new to vim, I misread I think.

nkraft18:03:06

@dominicm: I've just used vim for quick hacks on bash and python scripts. This venture into vim+clojure is the first time I've tried to use vim for serious development. I usually turn to emacs+cider for that, but I find I'm enjoying vim a lot.

dominicm18:03:20

I :heart: sexp.

dominicm18:03:36

It brings a bunch of text objects you need.

nkraft18:03:06

Though I dislike paredit in any editor.

dominicm18:03:20

Steve Losh used Clojure for a while, so he has some interesting configs for sexp. But he uses Paredit.vim as well, I need to check out what he uses each for.

dominicm18:03:05

paredit.vim pretty much just provides sexp (with weird mappings imo), and paren balancing.

nkraft18:03:10

If it's anything like paredit in Emacs, I do not want a set of commands or mappings for editing parenthesis, I want to manage them in my editor. I could rant about paredit all afternoon, but I won't. Suffice to say that I've disliked it for more than 10 years, and I don't think I'm going to "see the light" anytime soon. :simple_smile:

dominicm18:03:15

Interesting.. :stuck_out_tongue: I love the ability to just use a binding, and wrap an element in parens, move an element back and forth, etc.

nkraft18:03:27

Lots of people feel like you do about paredit. I know I'm in the minority. After years of common lisp and other lispy languages, I have muscle memory and a workflow that makes paredit feel like a rude guest in my editor.

dominicm18:03:04

I'm interested to see how you work more than anything :stuck_out_tongue:

dominicm18:03:52

It would be really cool.

snoe18:03:31

@nkraft well I think that same feeling was an inspiration for parinfer. I would like to hear a rant on paredit though, it's something I hear every so often but don't fully understand.

dominicm19:03:19

@snoe what did you use pre-parinfer?

snoe19:03:41

a mix of paredit and sexp

snoe19:03:07

now I'm using all three :simple_smile: because nothing is great

dominicm19:03:09

ah, why a mix? Which parts? Might I want to copy that? HMMM? :stuck_out_tongue:

snoe19:03:11

paredit for D handling mostly. sexp for movement, transpose, wrapping. parinfer for paren ballencing etc

dominicm19:03:48

Yeah, that's pretty much all I miss from paredit.vim, I thought so

dominicm19:03:02

I've managed to survive without by just doing "dae" generally.

dominicm19:03:19

parinfer handles D pretty well.`

nkraft20:03:00

I just have time for a mini-rant, but my biggest peeve is the way Paredit tries too hard to be "helpful" and enforce a way of writing code. If I have (fnc 1 2) and I want to add (a (fnc 1 2)) I want something to tell me when I don't match the parenthesis, but I don't want to hit '(' and get '() (fnc 1 2)' with a right parenthesis that I now can't move except with paredit's special commands. Changing (fnc 1 2) to (a (fnc 1 2)) takes me four keystrokes with no visual confusion. Paredit just doesn't improve on that.

nkraft20:03:30

I spend half the time using paredit with it disabled so it will get out of my way.

dominicm20:03:44

I agree there, vim-sexp has some insert mode mappings, and you can turn those off (without losing everything else)

dominicm20:03:27

although, I have become one with my editor in that case, and just do umm... ,i and it wraps turns (fnc 1 2) into ( (fnc 1 2))

nkraft20:03:17

My brain just doesn't think like that. When I want a parenthesis, my fingers hit the parenthesis keys. It does sound, though, like using paredit in vim might be a bit less trouble than it is in Emacs.

nkraft20:03:22

That's just me, though. Since I started coding before paredit was around, I already had a workflow and style when everyone jumped on the paredit bandwagon.

snoe20:03:43

Well wrap exists in emacs paredit, and I think that vim's paredit stuff is much less "helpful" than emacs. It does sound like you might enjoy parinfer

nkraft20:03:49

I'll give it a try. I just installed it in my vim. Seems a lot less heavy-handed than Emacs paredit. Llet's see how the rest of the day goes.

nkraft20:03:16

Thanks for the parinfer pointer.

dominicm20:03:07

vim is generally less rude

nkraft20:03:20

I'm getting that feeling about vim.