This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (4)
- # beginners (70)
- # cider (66)
- # clara (16)
- # cljdoc (20)
- # cljs-dev (9)
- # cljsrn (2)
- # clojure (36)
- # clojure-ecuador (2)
- # clojure-italy (14)
- # clojure-japan (2)
- # clojure-nl (22)
- # clojure-uk (79)
- # clojurescript (133)
- # clojutre (2)
- # code-reviews (5)
- # cursive (5)
- # data-science (1)
- # datomic (47)
- # duct (2)
- # emacs (1)
- # figwheel-main (3)
- # fulcro (11)
- # funcool (1)
- # graphql (6)
- # hyperfiddle (4)
- # leiningen (4)
- # luminus (9)
- # lumo (8)
- # mount (4)
- # nrepl (2)
- # off-topic (19)
- # onyx (1)
- # re-frame (23)
- # reagent (91)
- # reitit (17)
- # ring-swagger (2)
- # shadow-cljs (43)
- # tools-deps (27)
- # vim (45)
@alex.lynham not too bad really. We've built a little tooling to fill gaps, but mostly it does the job.
@alex.lynham The gaps are that it isn't a build tool, so there needs to be some written. We wrote https://github.com/juxt/pack.alpha to create uberjars from deps.edn descriptions, I also wrote https://github.com/SevereOverfl0w/krei.alpha to start trying to consolidate some build tooling for sass,cljs, etc. but haven't taken it too far. It doesn't depend on deps.edn at all though, just relies on the classpath. Overall, it encourages a good shift, writing code which works for lein/boot/clj rather than just lein plugins.
What it does better is mostly about what it doesn't do. It doesn't do a lot of things, and gets out of your way.
at the time he was working on https://github.com/RickMoynihan/lein-tools-deps I think (although quite a diff thing)
because I'm hacking around with this serverless stuff and it needs some quite heavy custom config to bootstrap, I'm hitting the edges of where lein is v good and so I'm sort of open to new ideas
yeah, that's a good way to use tools.deps.alpha (what underlies the clojure cli) with lein.
@alex.lynham in order to encourage your bad behavior, what is the custom config you're needing?
basically things like tricking figwheel into thinking there's a web stack when I'm basically just writing code in a buffer
so this is the part of the figwheel docs I mean. Nothing too egregious to be fair but https://github.com/bhauman/lein-figwheel/wiki/Node.js-development-with-figwheel#nodejs-standalone-application-development-with-figwheel
> Alternatively, you can set the autocommit attribute of the connection object to False. This ensures that psycopg will execute every statement and commit it immediately.
and there's the bug from yesterday. Silly me for thinking autocommit
True would enable autocommit 🙂
i’ve been enjoying learning new commands and seeing what it has to offer, i really like the git interface where its like a time machine and u can see previous and older commits as code in ur editor
@guy you know what they say “Spacemacs is an entry drug to Emacs!“…..Well, OK, no one says that..except me.
haha yeah i’ve really enjoyed emacs before, but im learning spacemacs as my friend is learning it too. So i can learn at the same time. I was quite happy with click adventures that is intellij 😂
also partly because there were two other emacs users in the office, so easier to garden config
I tried cursive but I found CIDER to be ahead of it in most features…and even with emacs keybindings Idea is still no emacs.
Just loads of little things…like the kill ring buffer in Idea is only about 5 previous kills
Unfortunately, I’m working on a large Java codebase atm and emacs is just not capable of refactoring, running integration tests with all the requisite plugins for extra sh*t in Java enterprise apps (Spring, Mockito, etc.), etc. Eclim is far too slow (constantly recompiles entire project on save which can take over a minute on a big project), JDEE buggy and has same recompilation problem as Eclim plus almost no support for Spring, Meghanada - good for small projects but can’t handle running tests that have specific dependencies on Spring and can’t handle long test method names, etc. If everyone used emacs maybe Java projects wouldn’t end up with long test method names, slow builds, etc. but I’m the only one!
Yeah but IDEA’s actual text editing is pants! I’m living half in one camp and half in ’tother. Lucky I have 2 monitors, Emacs in one and Idea in the other.
Does anyone have favourite examples of good guides to Emacs for Clojure that I might take inspiration from in order to write a vim one?
@peterwestmacott not sure what you mean. Spring is doing what it does. The problem is that Emacs Eclim doesn’t have all the hooks into the spring framework that Eclipse plugins or Idea plugins do. It’s the development lifecycle around refactoring, running tests, etc. that’s the problem. Runtime is fine using Spring. It’s mainly cos Emacs and it’s .el files can’t hook into Aspects which is how a lot of Spring stuff is implemented.
But I’m never going to get away from frameworks like Spring, DropWizard etc. in Java.
DropWizard is actually quite Clojuresque in a way - more a collection of libraries than a framework.
I’ve tried to write large complex apps without Spring….it’s a nightmare. It’s far from perfect but people forget what it’s like without it.