Clojurians Log v2
spacemacs
I might have found a bug in the syntax highlighter. Can anyone else reproduce?
def-ed strings with quotes seem to be interpreted as docstrings.
Yeah, that happens for me too.
Having trouble with Spacemacs. Has been working great for the last 2 years or so but today, for some reason, my *cider-repl* buffer stopped launching for no reason that I have been able to discover. I've tried multiple launching different projects, thinking maybe there was something in the configuration of a specific project, which did not work. I've tried creating a new project, which also did not work. I moved my previous .emacs.d folder to a backup location and create a fresh install of Spacemacs but no luck. Here is the tall end of the *Messages* buffer for the fresh install
Done (Total of 1 file compiled, 2 skipped)
(Spacemacs) --> installing package: yasnippet@auto-completion... [155/155]
Auto-evilification could not remap these functions in map 'edebug-mode-map':
- 'edebug-Go-nonstop-mode' originally mapped on 'G'
Auto-evilification could not remap these functions in map 'tar-mode-map':
- 'tar-chgrp-entry' originally mapped on 'G'
(Spacemacs) Warning: tern binary not found!
Loading /Users/marcusoladell/.emacs.d/layers/+distributions/spacemacs-base/keybindings.el (source)...done
Loading /Users/marcusoladell/.emacs.d/layers/+source-control/version-control/keybindings.el (source)...done
Loading /Users/marcusoladell/.emacs.d/.cache/recentf...done
Saving file /Users/marcusoladell/.spacemacs...
Wrote /Users/marcusoladell/.spacemacs [2 times]
Spacemacs is ready.
Open the quickhelp.
Start checking for new version...
Spacemacs is up to date.
[yas] Check your `yas-snippet-dirs': /Users/marcusoladell/.emacs.d/elpa/yasnippet-20200329.1434/snippets is not a directory
[yas] Prepared just-in-time loading of snippets with some errors. Check *Messages*.
[nREPL] Starting server via /usr/local/bin/lein update-in :dependencies conj \[nrepl\ \"0.7.0\"\] -- update-in :plugins conj \[refactor-nrepl\ \"2.5.0\"\] -- update-in :plugins conj \[cider/cider-nrepl\ \"0.25.0-SNAPSHOT\"\] -- repl :headless :host localhost
Quit
[nREPL] Starting server via /usr/local/bin/lein update-in :dependencies conj \[nrepl\ \"0.7.0\"\] -- update-in :plugins conj \[refactor-nrepl\ \"2.5.0\"\] -- update-in :plugins conj \[cider/cider-nrepl\ \"0.25.0-SNAPSHOT\"\] -- repl :headless :host localhost
<left-fringe> <drag-mouse-1> is undefinedMany of these warnings or errors I have seen before things went sideways today. Not sure if they are relevant to what is happening.
The nrepl-server launches successfully. I just don't get any *cider-nrepl* buffer connected to it. 😕
@mafcocinco The info from your message buffer suggests you have re-installed Spacemacs, or change Emacs versions or changed from develop to master branch (or vice versa). Specifically these lines
(Spacemacs) --> installing package: yasnippet@auto-completion... [155/155]
Saving file /Users/marcusoladell/.spacemacs...Or it could be that you have updated packages after a while, as 155 packages is quite a lot in one go. My monthly package upgrades only have about 20+ packages
Have you changed anything recently?
It doesnt seem like Emacs was restarted after all those 155 packages were updates, so that would be the first thing to try.
You seem to have a newer (probably newest) version of CIDER, as the messages say its adding nrepl 0.7.0. I am only running 0.6.0 and I did upgrade my packages not that long ago.
I just installed the latest clojure-mode package via the link on the Spacemacs Home buffer and ran a repl. The repl runs find and I can open the repl buffer and see that its connected. The only difference is that I am not using clj-refactor, so I do not have the nrepl-refactor library injected when I run the repl. So yo uhave the extra [refactor-nrepl\ \"2.5.0\"\] library injected. CIDER occasionally has issues with clj-refactor, but that is usually with older versions of both libraries and you are running new versions.
I suggest removing clj-refactor from the clojure layer in your .spacemacs config and see if that narrows down the issue, if a restart of Emacs did not fix the issue.