Janfel

I had the same problem, but after some experimenting, I managed to fix it. Note that this only applies to german quotes, not to french ones. It seems this issue...

I have found a workaround by using `sed` to rewrite `packer_compiled.lua` on `PackerCompileDone`. ```lua function() local file = require("packer").config.compile_path if vim.fn.filereadable(file) ~= 1 then return end local sed = vim.fn.exepath("sed")...

I am currently experimenting with something like that in my own config. This is what I have so far, feel free to use it until the devs get around to...

In the case of `yas-expand`, `describe-function` first produces the original function definition using `(nth 3 (help-fns--analyze-function 'yas-expand))` before passing it to `help-function-arglist`. This will not automatically solve `help-command` though, as...

I might look into improving the CLI, but that is a separate issue and out of scope for this PR.

I believe these are the problems we are trying to solve: 1. The current behavior is surprising and unintuitive. 2. Having to manually specify the mode is “stating the obvious”...

I also experience this issue on Manjaro with the Manjaro package (`0.2.0`), the Arch package (`0.2.1`) and the Arch/Manjaro package built from scratch using [this PKGBUILD](https://github.com/archlinux/svntogit-community/blob/1c1db542305f84bc8a2e72edcc0917db994ac6c4/trunk/PKGBUILD) with `rustc`/`cargo` version `1.64.0`....

`howl

You can probably use something like the [Rockspec Format] used by [LuaRocks]. They are loading the files like regular Lua modules, just with an empty environment. This, however, would be...

One could always just use a weak sandbox on the client and expect the user to know what they are downloading (like Vim) or provide the majority of bundles in...