Fork me on GitHub
#clojure-uk
<
2019-02-05
>
mccraigmccraig10:02:48

anyone got any favoured solutions for emacs-based collaborative code editing / browsing ?

dominicm10:02:12

haven't tried it on emacs, but it worked good on vim

mccraigmccraig12:02:46

thanks - seems to work ok on emacs too @dominicm

otfrom13:02:49

tho I've not used floobits before

mccraigmccraig13:02:50

floobits seems to work ok without forcing me to use emacs in a terminal... i can do it, but i'm sadly wedded to trackpad scrolling so it's a bit painful

mccraigmccraig13:02:37

(i recently changed my emacs runtime to get smoother scrolling)

agile_geek13:02:26

I've used floobits a little. I think it's the best cross editor option out there by a mile.

mccraigmccraig14:02:00

it worked quite well from emacs... bad from atom though - you couldn't share anything less than the entire project you are working on, which is less than ideal in a monorepo world

agile_geek15:02:18

yeah not sure it's built for monorepo in mind. I've used in from Emacs and IntelliJ Idea and it worked ok but Idea was same as Atom in that the entire project is shared.

agile_geek15:02:14

I was actually using it on a Java project not Clojure but Floobits obviously doesn't really care.

yogidevbear16:02:18

TIL:

(= #:example{:foo "bar"} {:example/foo "bar"})
;; true

yogidevbear16:02:13

And

(merge #:example{:foo "bar"} #:sample{:baz "bat"})
;; {:example/foo "bar", :sample/baz "bat"}

yogidevbear16:02:52

Sorry if everyone else knew about this already. It came as news to me 😊

minimal16:02:15

also

(let [{:example/keys [foo]} #:example{:foo "bar"}] foo)
"bar"

rickmoynihan15:02:02

Also

(set! *print-namespace-maps* false)

mccraigmccraig16:02:46

i rarely use :keys, i find the longer binding form much more readable (let [{foo :example/foo} #:example{:foo "bar"}] foo)

Rachel Westmacott17:02:23

Huh, I love :keys and use it almost exclusively.

mccraigmccraig17:02:50

i used to use :keys a lot, and then i found i was running out of steam with it - it's not so good with destructuring nested maps or changing names for binding - so i ended up preferring the more flexible long form because using just one or the other makes for much easier code comprehension, and i ended up with better bound names more often with the long form, so the extra verbosity was a price worth paying

👍 5
practicalli-johnny21:02:48

Bohemian Git-sody... I found this rather fun, although it could be the Guinness talking https://twitter.com/JordanHawker/status/1090933555067158529?s=19

😂 10