danirukun

Also I think that the development guides in https://github.com/elixir-lsp/elixir-ls/tree/master/guides should probablly move into `docs` and be available in the docsite. Of course want to hear your comments about this idea.

@lukaszsamson they are not removed, they have already been moved to the docsite. E.g. see https://elixir-lsp.github.io/elixir-ls/getting-started/vscode/#debugger and https://elixir-lsp.github.io/elixir-ls/features/ This is to keep the README clean and only have the most...

I have to agree with @lukaszsamson - a trunk-based approach in this case is much simpler and avoids the complexity of having to now deal with an additional branch. If...

Was thinking the same, I can ask our graphics designer this week if they have some time to make a couple variations.

Sure! I've already done something similar for ElixirLS, for ErlangLS should be even simpler 😄

There is also outdated info in https://github.com/hlissner/doom-emacs/blob/develop/modules/lang/erlang/README.org , especially related to the Language Server and the completion package.

IIRC this was fixable by add `(require 'cl-lib)` to the top of the package.

I also have an issue when calling any `screenshot` command on macOS Monterey, but a bit different: ``` cl-no-applicable-method: No applicable method: clone, nil, :prototype, nil, :level, 4 [3 times]...

Potential workaround might be implemented in the image building steps like described here: https://forums.opera.com/topic/27474/please-explain-to-this-rookie-how-to-install-codecs-to-make-videos-work/5?lang=en-GB Seems the core issue is that vanilla Opera doesn't come with any h264 decoder or ffmpeg.

I normally just do the analysis as mentioned in the examples, then in the matplotlib window I press "save" and save the rendered plot as whatever filename I want.