This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-08
Channels
- # aleph (2)
- # aws (1)
- # beginners (172)
- # boot (15)
- # cider (17)
- # clara (7)
- # cljs-dev (22)
- # cljsrn (12)
- # clojars (3)
- # clojure (110)
- # clojure-dev (5)
- # clojure-italy (13)
- # clojure-sanfrancisco (5)
- # clojure-spec (3)
- # clojure-uk (31)
- # clojurescript (110)
- # community-development (2)
- # cursive (16)
- # datomic (19)
- # docs (4)
- # emacs (49)
- # fulcro (24)
- # jobs (5)
- # keechma (2)
- # lein-figwheel (41)
- # leiningen (10)
- # luminus (4)
- # lumo (24)
- # mount (24)
- # numerical-computing (1)
- # off-topic (16)
- # om (4)
- # onyx (6)
- # parinfer (9)
- # planck (8)
- # re-frame (7)
- # reagent (6)
- # shadow-cljs (125)
- # sql (5)
- # test-check (9)
- # unrepl (6)
- # yada (5)
for those coming from a scheme / clojure background, dash.el is tye library that intuitively makes sense right ?
@qqq Emacs Lisp has a long history and it’s focus has never really been FP. dash.el
was one attempt to bring some of the lessons learned from Clojure, and it was quite the success.
Eventually Emacs added upstream seq.el
and map.el
which are amazing libraries imo, plus things like thread-first
, thread-last
, when-let
, etc.
At this point dash.el
is irrelevant, but it was instrumental in pushing Emacs Lisp forward.
@bozhidar: Will you consider writing a "elisp for clojurists" guide some day? I suspect many of us can learn a lot from you.
why not just clojure.el
😜
I may have just nerd sniped myself in working on that this weekend
@bostonaholic: where is clojure.el ? Google is giving me all types of clojure-mode results
I don’t know if it exists. I was just suggesting that it should exist
since you mentioned “elisp for clojurists”
why not just write an elisp lib that brings clojure to elisp
that’s why I said I probably nerd sniped myself. Which is a way of saying “I think there should be this thing. Shit. Now I want to build said thing.”
I accept BTC and BCH 😜
I was unfamiliar with the term "nerd sniped" -- take a look at https://github.com/mogenslund/liquid -- it's the most promising I've seen so far.
It has console, java/awt, and cljs/dom/web browswer front end. It's 100% scriptale in clojure.
@bostonaholic: in paritcular, I think "build editor/IDE on clojure" is better in the long run than "build a clojure-like lib on top of emacs lisp"
That assumes that Clojure is all you care about, but I personally have interest in many areas and prefer using universal tools instead of specialized.
@bozhidar: that is absolutely true. I currently use two languages: clj/cljs/cljc + ELisp I'm trying to reduce it down to one: clj/cljs/cljc
After getting rid of emacs, next step is to get rid of the shell, and do all scripting in the repl too.
The other thing is: as long as we want general edito rsupport, we're going to use something like the "sliing buffer", where we store "text before cursor" "text after cursor" whereas I really really want a structural editor
@qqq Do you see a benefit of only one language?
No assumptions, just a question
So here's the thing, if you build an editor that supports multiple langauges, the focus is "w3e want to build thsi generic interface, --- and if we can't do this in python/ruby/.... maybe we shoulnd't do it for Clojure."
Whereas, if, starting out, one says "fuck it, all we care about is Clojure", there can be very deep repl/jvm integration.
And I'm not saying we ban other programming languages -- they can continue to use vim / emacs / textmate / atom / ...., I'm just saying we should build an editor/ide taht focuses solely on Clojure + JVM integration, andnot give a damn about any other language.
I agree, Everything in every language > everything in clojure > some things in every language.
However the shell is nice too, things like sed are pretty handy to have lying around
Also, in shell, you can really only pipe streams of text. With (-> ...) you can pipe streams of STRUCTURED DATA 🙂
The two are able to coexist. Sed can manipulate some sttructured text and return it with only string replacements then clojure can read the string and do stuctural manipulation. I don't personally do it, but I find it hard to say it would be impossible to be useful
If I had a clojure shell, I don't see any reason I'd ever use sed / grep / awk instead of Clojure's regexps.
I suppose if you never wanted to do anything new with the hardware, you wouldn't run into a use case where you would need the system
=====
I am not sure if this is an Emacs issue or an Evil issue.
Suppose I do a regex search on a pattern of the form "^..."
then I do (goto-char (match-beginning 0))
is this supposed to :
1. put me on first char of matching line OR
2. put me on last char of previous line?
Because I am expecting (1), but getting (2) -- and I don't know if this is an emacs issue or an evil issue.