@axelson in the spacemacs part it is worth to specify either link to the layer doc about backend or write here, that in the layer definition you should set the backend
(elixir :variables elixir-backend 'lsp)
as alchemist is still the default backend (left it so, for backwards compatibility as elixir-ls requires additional step of installing the server itself)
Hi, does anyone meet the error “Too many open files” in spacemacs when lsp is watching many files?
Loading /Users/james/.spacemacs.d/init.el (source)...done
Starting a server...
Spacemacs is ready.
Loading /Users/james/.emacs.d/.cache/recentf...done
Skipping check for new version (reason: dotfile)
[yas] Prepared just-in-time loading of snippets successfully.
LSP :: Connected to [elixir-ls:53015 status:starting].
LSP :: Connected to [elixir-ls:53267 status:starting].
init.el has auto save data; consider M-x recover-this-file
There are 14222 files in folder /Users/james/src/evercam_wechat/ and watching the repo which may slow Emacs down. To configure:
1. Use `lsp-enable-file-watchers' to disable file watchers globally or for the project(via .dir-local).
2. Increase/set to nil `lsp-file-watch-threshold' to remove the warning.
Do you want to continue? (y or n) n
There are 3013 files in folder /Users/james/src/brightu_umbrella/ and watching the repo which may slow Emacs down. To configure:
1. Use `lsp-enable-file-watchers' to disable file watchers globally or for the project(via .dir-local).
2. Increase/set to nil `lsp-file-watch-threshold' to remove the warning.
Do you want to continue? (y or n) y
LSP :: Connected to [elixir-ls:53267]. [3 times]
File local-variables error: (file-error Creating pipe Too many open files)
[persp-mode] Error: Can not autoresume perspectives -- (file-error Cannot redirect stderr Too many open files /dev/null)
user-error: Minibuffer window is not active
evil-line-move: Beginning of buffer [6 times]
evil-line-move: End of buffer [10 times]
Quit
The config is following:
(elixir :variables
elixir-backend 'lsp
elixir-ls-path "~/src/elixir-ls/release")
Too many open files can happen everywhere…
Please check the ulimit -n, perhaps even increase the limits of emacs parent environment (depending on how you start it).
Thanks, I’m on macOS, the default value is 256. Set the max open files limits and problem solved.
sudo launchctl limit maxfiles 65535 102400
Hi, did you figure this out? The codebase that I work on enforces strict credo standards so it would be nice for me to have credo working properly on save, just like it does under alchemist. For me the situation is exactly as you described, i.e. credo messages only show up upon lsp-ui changes.
Hello folks, does anyone have this issue with spacemacs develop branch?
If the post does not belong to this wiki, I will delete and create a separate post. Thank you!
@SZJX
I don’t think the issue is connected to lsp-mode or emacs in general.
lsp-mode will only report errors/warnings, that elixir-ls passes it. So in order to integrate credo to
lsp-mode it should be implemented in elixir-ls. I don’t know if elixir-ls has any kind of plugin endpoint though.
I.e. In python world there is a bunch linters you can use. If you want them to work with lsp, you need to add a plugin of that linter to python-language-server. So the ls will report messages from that linter to lsp-mode client.
We don’t need lsp-mode to report the warnings, because credo has its own flycheck plugin. Lint checkers for many languages work the same way, we just have to do a flycheck-add-next-checker. For example this configuration works fine for me for chaining hlint behind intero-mode in Haskell:
(flycheck-add-next-checker 'intero
'(warning . haskell-hlint))
Using the same method for Credo & LSP Mode does not work. I don’t know if you read my original message, but the problem is not that warnings are never reported. It is that they are not dismissed correctly, and may be masked if lsp-mode doesn’t have its own warnings to report.
One difference with the Elixir checker is that it only runs on save, I’m not sure if thats why the problem exists.
I haven’t gotten a chance to try it out yet, but since this is a wiki feel free to go ahead and edit the wiki yourself 