Clojurians Log v2
spacemacs
The command cider-eval-list-around-point has been added to the recently released Cider 0.26 version, so I created a pull request on Spacemacs repository to add a key binding to the Clojure major mode menu. I've chosen SPCE m e ( as the keybinding as l was already taken in the evaluation menu.
Feedback and reactions are welcome on the pull request page
https://github.com/syl20bnr/spacemacs/pull/13991
I'm having this problem, which I think is a path problem, and none of the methods I can find via googling are helping. I switched from a Linux box to a MacOS machine. I cannot for the life of me figure out how to explain to my typescript layer how to find the node executable [SOLVED]
Someone had a similar problem with their haskell compiler, and they added a path line to /etc/paths; this did not help
Other people have described using executable-find and process-lines to understand how things are set in their emacs, but those commands don't appear when I do SPC SPC
I created a zshrc file that inclues the executable path, so now when I open the emacs shell (I don't usually use it) and say which node
the program is found
but the tide-server still cannot find it
that MIGHT imply it's a problem with the layer? my next step is checking the issues page there
well I added some variables here and made sure that I'd npm installed everything mentioned https://develop.spacemacs.org/layers/+lang/typescript/README.html
but still node is not found
i didn't have trouble on my linux box so I'm having trouble figuring out what could be wrong 😢
GOT IT
to my shock and alarm, SPC SPC
doesn't find executable-path
but M-: still lets me execute that
:man-shrugging::skin-tone-2:
To help troubleshoot paths and environment variables with Spacemacs:
SPC f e e opens the spacemacs.env file which automatically generated when running Emacs, populated from the operating system path. So you can always check that file to see if the right path is being picked up.
Its possible to add environment variables here, for example adding things to the path.
Ideally the path would be fixed in the OS layer, if not then adding to the spacemacs.env file might help
that's a great tip, thanks!