search

flyingmachine / emacs-for-clojure

519 stars 267 forks source link

"Symbol’s function definition is void: sesman-current-sessions" #43

Open nerdcha opened 5 years ago

nerdcha commented 5 years ago

Howdy! The current version of Cider seems to depend on the patch to sesman that was pushed six months ago, which introduced something called sesman-current-sessions. I was able to get around this by editing my copy of init.el to include

(add-to-list 'package-pinned-packages '(sesman . "melpa-stable") t)

(Also: would you consider adding a license to this repo? That would have let me send this as a PR 😁)

MalloZup commented 5 years ago

Thx for this repo and project first, it is really helpfull ! :cupid:

I had the same issue, and i fixed updating the sesman pkg. However i think that this error is really affecting the global User Experience of the guide, e.g: if somebody is new to emacs and also want to learn cider and other nice stuff, this should work and we shouldn't assume that the user can fix, and digging into all the emacs details pkging when we can simplify the experience, since the User at begin wanted to learn cider and emacs

locphan87 commented 5 years ago

reinstall sesman (M-x package-reinstall) works for me. By the way, as a new emacs user, it takes me a while to figure it out.

rr326 commented 4 years ago

I had the same issue and it was resolved with some help from Cider: https://github.com/clojure-emacs/cider/issues/2704. Wish I had looked here first! @flyingmachine Suggestion: it seems like you are including the actual source files for cider, etc. Maybe you can not include them and just let emacs install from latest? That worked in my case.

okc0mputer commented 4 years ago

This is the reason I don't use emacs. Yeah its got tons of features, but its a real pain to get working even if the config is provided for us. For the book I would suggest atom with the proto-repl plugin, because it just works.

ulrichschinz commented 4 years ago

For me (as trying to checkout emacs, coming from vim) the best way to do it, was to just remove everything from the elpa directory and starting emacs. This installed all packages in an up to date version and it worked without any further customizations... thx @rr326 for mentioning to let emacs do the install job ;)

flyingmachine commented 4 years ago

thanks for all the feedback and suggestions on this everyone, and I'm very sorry that you've had to deal with this issue.

I've updated the included packages so hopefully people won't experience this issue in the future.

It'd be great to remove the packages from the repo and just let emacs do the work! In the past I've run into issues where emacs would install versions of the packages that would cause problems, and I don't know of a way to control package installation so that everything is sure to work. If anyone has suggestions there I'd love to hear them :)