emacs

Consider also joining #cider, #lsp and #inf-clojure, where most of the tool-specific discussions are happening.
Snaffu 2020-05-12T11:42:54.293Z

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

dpsutton 2020-05-12T22:09:05.293900Z

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

Eric Ihli 2020-05-12T22:40:21.296Z

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

dpsutton 2020-05-12T22:40:53.296300Z

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:

((nil
  (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

iarenaza 2020-05-14T21:51:05.298400Z

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

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

dpsutton 2020-05-14T21:52:11.298600Z

i think that evals on every buffer though unfortunately

dpsutton 2020-05-14T21:52:18.298800Z

ah, the setq local. i like it

dpsutton 2020-05-14T21:52:31.299Z

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

iarenaza 2020-05-14T21:53:27.299200Z

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.

dpsutton 2020-05-12T22:41:11.296600Z

and thanks @ericihli

Eric Ihli 2020-05-12T22:46:46.296700Z

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 Ihli 2020-05-12T22:47:46.296900Z

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.

dpsutton 2020-05-12T22:48:28.297200Z

you're probably right. thanks!

🤙 1