cider-jack-in just works
cider-jack-in errors out with Symbol’s function definition is void: sesman-linked-sessions
M-x cider-jack-in
l0.18.0
Include here the version string displayed when
CIDER's REPL is launched. Here's an example:
;; CIDER 0.18.0 (Saigon), nREPL 0.2.13
;; Clojure 1.9.0, Java 1.8.0_181
;; Docs: (doc function-name)
;; (find-doc part-of-name)
;; Source: (source function-name)
;; Javadoc: (javadoc java-object-or-class)
;; Exit: <C-c C-q>
;; Results: Stored in vars *1, *2, *3, an exception in *e;
GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.22.30) of 2018-05-28
Ubuntu 18.04
This is probably something really stupid and simple, but my google-fu is failing. I'm also a LISP/Clojure/Emacs noob, so apologies in advance.
Vanilla Emacs, installed latest packages through Emacs' package manager. Nothing crazy.
CIDER is attempting to call sesman-linked-sessions which doesn't exist in Sesman, seems like it was replaced by sesman--linked-sessions which should be ok since the new function is aliasing the old one here - https://github.com/vspinu/sesman/blob/14475d8192a785568a23f274f7715b1509da93ea/sesman.el#L976
Yet for whatever reason that alias isn't working on my machine. I changed the function call to sesman--linked-sessions in cider.el and voila - cider-jack-in works!
The fact that the alias isn't working and me being the first to discover this leads me to believe it's not a real bug but something silly I'm just not seeing on my end.
I am not able to reproduce this, with latest CIDER from MELPA.
I think upgrading to the latest sesman version from MELPA should fix this.
I can reproduce this error with sesman v. 0.3.2. I've had to revert to git tag v.0.3 to regain cider functionality.
Edit: emacs 26.1-2, cider 0.18.0
Phew. Glad I'm not the only one. Out of curiosity - shouldn't the define-obsolete-function-alias call in Sesman prevent this from happening? General ELISP question perhaps.
There was an issue at the sesman repo which says that the issue was resolved and that we'd just have to wait till the update reaches Melpa. However, that was 4 days ago and the issue remains - could the update take that long to reach Melpa?
Both cider and sesman are up to date in MELPA. You must be using an older version locally. New cider doesn't use sesman-linked-sessions anymore.
Same issue for me as well after just updating cider.
Will try updating sesman to latest in MELPA
FYI: Updating sesman to latest in MELP fixed this particular problem.
Ah yes, just checked my init.el - I'm on Melpa Stable, having left Melpa some years ago. So I'll just wait till the fix percolates there. In the meantime I'm just using a workaround mentioned on Reddit.
Arh, this makes sense. I have just pushed a new version tag to sesman to avoid issues with melpa stable.
Thanks Vitalie, much appreciated!
Edit: The update landed on Melpa Stable and all is good again. Thank you!
On Thu, Oct 18, 2018 at 5:29 PM Vitalie Spinu notifications@github.com
wrote:
Arh, this makes sense. I have just pushed a new version tag to sesman to
avoid issues with melpa stable.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/clojure-emacs/cider/issues/2491#issuecomment-430973646,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWrv-MHYT-nNPY-1-Wtg6rmie35Gsz5ks5umGYzgaJpZM4XjGmN
.
Most helpful comment
FYI: Updating sesman to latest in MELP fixed this particular problem.