Fork me on GitHub
#cider
<
2015-07-02
>
bozhidar06:07:27

@otijhuis: document a great setup is not hard, but we’re all lazy simple_smile

jrychter07:07:14

Going back to package discussion — the problem with MELPA is that it provides a ton of "latest" packages with newer versions than stable. Once you add MELPA, you can't just upgrade everything, or you'll upgrade your whole setup to the latest and greatest bleeding edge versions. And as to "pinned packages", the problem is that you can pin one package to a particular repository, but you can't say "I only want this package from this repo". So it doesn't solve the MELPA problem.

malabarba08:07:36

@jrychter yes, that's always been the problem with Melpa. There's a whole discussion on why they decided to go this way, but the end result is that using Melpa means package.el will always try to upgrade your to the bleeding edge. That is, before 25.1.

jrychter08:07:57

This 25.1 thing sounds seriously good.

malabarba08:07:34

Ok. Now I promise I'll stop bringing it up. :-)

andrea.crotti09:07:45

I think we also have to keep in mind that package management in Emacs is quite new

andrea.crotti09:07:10

and Emacs users didn't have any for > 25 years probably

jwm11:07:17

I’ve been running gentoo with ~amd64 for 15 years

jwm11:07:06

though I can only assume bleeding edge packages in emacs are a bit different from those in nix land heh

bozhidar12:07:59

it’s not the same

bozhidar12:07:25

in Gentoo all packages are still built from “released” tags/branches

bozhidar12:07:34

they might be new, but they were officially released

bozhidar12:07:44

in MELPA the packages are just snapshot of the development branches

bozhidar12:07:53

usually the packages themselves work

bozhidar12:07:26

but often the changes in one package are breaking the ones that depending on them

malabarba12:07:09

Although, TBH, that hasn't happened to me that often anymore

malabarba12:07:32

And whenever a package is behaving a little odd, I usually find an update for it on the next day

malabarba12:07:19

The Emacs community has really adopted the habit of reporting bugs in the last year or two, which helps a lot.

bozhidar14:07:56

yeah, I often say GitHub saved Emacs

bozhidar14:07:20

it has never been so easy to report & fix problems and to learn modern Emacs Lisp practices

bozhidar14:07:37

I’ve been using Emacs for about a decade now

bozhidar14:07:54

but didn’t write pretty much anything until the GitHub era began

benedek14:07:04

pretty much the same here

andrea.crotti14:07:06

yeah me too, and emacswiki was such a mess but still got lot of stuff from there

bozhidar14:07:43

a while back in a moment of huge frustration with the wiki I wrote http://batsov.com/articles/2012/03/20/die-emacswiki/

bozhidar14:07:13

now, it’s significance for the community has shrunk and I don’t really care if it will ever be improved or not

jcsims14:07:36

@jrychter: you can pin packages to an archive in current stable emacs

jcsims14:07:48

that’s how I stay on cider and clojure-mode stable releases

jcsims14:07:21

(when (boundp 'package-pinned-packages)
  (setq package-pinned-packages
        '((cider        . "melpa-stable")
          (clj-refactor . "melpa-stable")
          (clojure-mode . "melpa-stable")
          (paradox      . "melpa-stable")
          (smartparens  . "melpa-stable"))))

enn15:07:36

It’s incredible how much more comprehensible (and shorter) my emacs config got when I started using real packages and use-package vs requiring bits and pieces of files from EmacsWiki

jcsims16:07:26

one of these days I need to check out use-package again

gtrak16:07:30

I use el-get for almost everything now.

gtrak16:07:34

it's lovely