This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-01-04
Channels
- # announcements (1)
- # babashka (1)
- # beginners (84)
- # biff (22)
- # calva (9)
- # cider (8)
- # clerk (5)
- # clj-kondo (10)
- # clojure (105)
- # clojure-europe (13)
- # clojure-nl (1)
- # clojure-norway (44)
- # clojure-spec (4)
- # clojure-uk (6)
- # clojuredesign-podcast (36)
- # cursive (13)
- # datomic (24)
- # dev-tooling (8)
- # emacs (8)
- # hyperfiddle (4)
- # jobs (1)
- # leiningen (2)
- # london-clojurians (1)
- # lsp (5)
- # malli (6)
- # membrane (11)
- # nyc (1)
- # off-topic (14)
- # other-languages (8)
- # pathom (25)
- # pedestal (2)
- # re-frame (4)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (98)
- # sql (5)
- # squint (1)
- # tools-deps (38)
- # vim (8)
- # xtdb (11)
Not sure if anyone is able to help me here, but I am running emacs inside of wsl, and something goes wrong when I try packages like eg. project-dired:
wrong type argument listp, d
My emacs config is taken from: https://github.com/magnars/.emacs.d
In addition I struggle with getting bin files to be at my shells path. (Fixed by putting (exec-path-from-shell-intialize) in my init file)
Lastly, I have gotten copy into emacs to work, but not yet found any way to copy text out of emacs.
my settings repo: https://github.com/hagenek/emacs.d/tree/main
regarding the paths; I've found https://github.com/purcell/exec-path-from-shell to work quite nicely (although it does add a bit to the startup time), particularly when using tools like nvm
as far as I known (which isn't much) the exec-path
variable lists all the paths emacs uses when running external processes, so you can inspect it to check if the paths are present
btw, I'm not sure if it's a good idea to include eln-cache
in your repo; aren't those binary files created by native compilation?
Adding (exec-path-from-shell-intialize) did the trick for the jack-in command. Now I just have the project-dired issue:
wrong type argument listp, d
perhaps enabling M-x toggle-debug-on-error
and looking at the stack trace might tell what's going on? Usually when I encounter something like that it's usually caused by too old/new version of some library/tool.
For copying out of emacs, this article can be useful: https://emacsredux.com/blog/2022/01/04/dealing-with-clipboard-issues-on-windows-11-wslg/