Fork me on GitHub

@jr0cket - thank you for the link, will definitely check out your channel 🙂


setting up a coworker with spacemacs. anyone know how to evaluate random elisp in the minibuffer? in vanilla its just M-: ...

Eric Ihli22:05:21

(describe-function 'eval-expression) wherever you can and that should tell you what shortcuts are available for it.


does anyone have a good idea on how to do dir-locals with many users in the company? finally have another emacs user and now need to not hardcode my stuff in dir locals. for example:

  (cider-path-translations . (("/root/" . "/Users/dan/") ("/src/" . "/Users/dan/projects/")))
  (cider-redirect-server-output-to-repl . nil)))
the path translations can't talk about `/Users/dan/' anymore. anyone have a good way to organize these? I don't want to setq them since its not the only project we use

Eric Ihli22:05:46

Might not be worth much effort to share dir-locals in any way other than a template/script that everyone can customize and make their own. Add .dir-locals to .gitignore and commit a .dir-locals.template that people can use as a reference.

Eric Ihli22:05:46

But if the org is big, or growing, and you do want to standardize, then you could use something like Ansible for dev workstation provisioning. I know most people use it for server management/provisioning. But it works just as well for local stuff.


you're probably right. thanks!

🤙 4

@U11BV7MTK In case you are interested, this is what I have, so I don't have to tweak project by project:

  . ((eval . (setq-local cider-path-translations (list (cons "/app" (clojure-project-dir (buffer-file-name (current-buffer))))))))))


i think that evals on every buffer though unfortunately


ah, the setq local. i like it


i wish there was something built in that would just set it once but that's pretty nice


Yes, that's the idea. I can have several projects open, each with different (non prefix shared paths) and every one picks its own translation paths.