This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # beginners (16)
- # boot (22)
- # cider (96)
- # clojure (146)
- # clojure-dev (5)
- # clojure-germany (7)
- # clojure-greece (3)
- # clojure-italy (5)
- # clojure-japan (76)
- # clojure-russia (6)
- # clojure-seattle (1)
- # clojure-sg (1)
- # clojure-uk (19)
- # clojure-ukraine (1)
- # clojurescript (114)
- # code-reviews (11)
- # datomic (42)
- # editors (4)
- # euroclojure (3)
- # jobs (18)
- # ldnclj (59)
- # off-topic (1)
- # om (17)
- # reagent (5)
- # yada (43)
@bruceadams: cider doesn’t do any dep management of its own; this is the responsibility of your build tool
for lein users this might be helpful - https://groups.google.com/forum/#!topic/leiningen/u-esr2zK690
for some reason it seems that Clojurians don’t care about source jars as much as Java devs used to care
@bozhidar: not sure about that. As Java dev for 19 years I probably look at Clojure source more than I ever did Java…but that might be it’s a good way to learn best practice in Clojure?
lein pom; mvn dependency:sources incantation suggested by Hugo Duncan in that thread definitely grabbed the sources … I still don’t have them in my classpath but I think I can figure out that part. Thank you for the link bozhidar!
downloading them is not enough, they have to be on the classpath so that source lookup algorithm will pick them up
It doesn’t seem to by default. I think I might need to add the
:classifier “source” to the project.clj. But I’m hoping I can find a way to do this generally without having to modify each project’s definition.
if you do - share it with the rest of us As said - this should be done by something like CIDER, but by the tools that boot the nREPL server
but it seems neither lein, nor boot care much about the sources (at least out of the box)
Should I expect breaking changes when upgrading from 0.8.2 to 0.9.1? I upgraded (upgraded the cider-nrepl middleware too) and I don't get the repl buffer and evaluation doesn't work. Thought I'd ask before I go into debugging.
@jrychter try uninstalling cider and clojure-mode, restarting emacs, then installing again.
For the reference, I'm running emacs 24.5.1 on OS X. And I don't think this should happen…
It's pretty rare. But it's a known issue and cider seems to have done something to step right on it. (not that it's cider's fault) :-)
In fact, the best way to avoid that issue is to keep your packages always upgraded.
But, like I said, it's pretty rare. Cider is only the second package I've seen suffer from this
Oh, no, I tried that. It's a road paved with pain. Some packages will require versions from different repos, I can't add "melpa" without adding a ton of packages with weird version numbers, and there is no way to say "use melpa for this one package only".
Of course this is not actually addressed at cider, just at the overall emacs package situation, which I think is really bad.
I have marmalade and melpa-stable configured permanently, and I sometimes switch melpa on just for a moment (my hotes say it's for rainbow-identifiers, dash-at-point and names).
Yeah, you should be able to use just Melpa stable, but some packages erroneously release stable versions that depend on unstable versions.
I dream of the day when I'll be able to just use things in emacs, without fiddling around with packages and downloads. I actually find it amazing — with the extensibility of emacs being tens of years ahead of anything else, its packaging story is years behind. Anyway, enough ranting. I hope things will improve somewhat soon
Tromey really did a fantastic job with package.el. He just didn't expect it to grow so fast
Anyway, On 25.1 there are archive priorities, so you'll be able to have Melpa configured and only use it as a last case resort.
you can pin packages -- i do this for cider https://github.com/derekslager/dotfiles/blob/master/emacs.d/derek/package.el#L10
Does anyone know the easiest way to get emacs with a specific configuration, clojure etc, installed without people having to jump through lots of hoops? Want to create some emacs tutorials for emacs/cider/clj-refactor etc. A VM actually might be the easiest way I think, unfortunately.
This was the way I entered emacs and clojure worlds (at the same time): https://github.com/overtone/emacs-live
@otijhuis: well a VM is never a great experience, and in the end you only need Java + lein + Emacs
if someone is not able to install that on his machine he/she not going to go far with Clojure imho
for the Emacs configuration there are many very easy options, but yeah just put a configuration in github
@andrea.crotti: understand where you're coming from but trying to make it easy to try out. A proper windows version of emacs wasn't easy to find. If you search for one for OSX you get multiple recommendations as well. Have an existing emacs configuration already? You have to replace it or fiddle with your home location. I know you should be able to figure it out but it's not a great first impression.
and yes I don't really enjoy using Emacs on Windows (or do anything else really)
Cursive I highly recommend, it's great. But at EuroClojure I noticed that quite a few people, who use emacs for clojure development, don't know about a lot of useful packages or functions. The tutorials will be specifically for clojure in Emacs.
But being reasonably easy to set up and not mess with current emacs configuration means a VM is probably the only option. Would prefer not using one but with osx/linux/windows and so on it's probably the 'easiest'
it was the first popular 3rd party repo, but the package submission process was pretty flawed
submitting packages often didn’t work and a lot of people had submitted the work of others
this made them owner of the packages and the actual authors couldn’t update them properly after this
but pretty much everyone had chosen the easy way of MELPA (and MELPA Stable afterwards)
while MELPA is definitely not for everyone it works pretty well, if you know your Emacs (Lisp)
* putting several packages in the same repo (which results in all of them having the same version in MELPA stable)
* people not updating the headers of their packages (resulting in stale dependencies)
I dream of us having the ability to deploy packages, the way we’re doing in Clojure/Ruby land
and having to jump through a web ui to submit a package (not to mention having to build the package archive manually first) is super tedious
I’ve been meaning to write an article about the sorry state of Emacs package for a while now
Anyone know what might be the cause of
foo.clj is in a bad state! for a number of clj-refactor operations?
FWIW, I was quite happy maintaining my load-path myself, downloading files manually and running a Makefile every now and then. I use cider from a cloned repo. 😄
@meow: I know. But got the emacs configuration covered. Going to use a minimal set just for Clojure. Spacemacs does way too much for my taste (I'm too picky and a community configuration just doesn't work for me). It's the whole environment you have to set up that's bugging me atm.
generally you need just 4 packages to be productive -
paredit (or equivalent) and
True, but adding some extra's as well. Not truly needed but make it a lot nicer to work with everything (clj-refactor of course, projectile, ido/smex/helm stuff). Just leaving out all the other languages and things you don't use with Clojure. It's just for tutorials from beginner to more 'advanced' stuff so people can see what's possible.