mralusw

This PR seems to just... work? Anyway `vim` is (as of now) at `9.1`.

Sorry, I meant this for @zivyangll ; I was wondering why this is not merged (i.e. are there any remaining problems?)

`EPOCHREALTIME` and `EPOCHSECONDS` are essential for benchmarking scripts. It's impossible to measure something if the process of measurement adds an unpredictable overhead to an external command, which probably itself has...

> > EPOCHREALTIME and EPOCHSECONDS are essential for benchmarking scripts. > > @mralusw If you want to profile a script, use `fish --profile`. That's very useful but it only handles...

> And that is why this issue is still open. The question is mostly where to put the functionality - $EPOCHREALTIME is a mouthful and quite jargony, a `status` subcommand...

> https://github.com/AppImage/appimagetool/releases Hm... there's a continuous build, but the last release (and commit, I guess) dates back to 2023-07

Thanks for the prompt response. I've bisected it to 895d448. That's where the `EACCESS` error starts to appear. Before that commit, it runs without errors.

I've also tried `nodejs=18.12.1-deb-1nodesource1` as recommended by [`nodejs.org`](https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions). Same error, also starting at 895d448 (with node 18 I also get an `EBADENGINE Unsupported engine` during `npm install`, which seemingly doesn't...

Great idea — I've just force-pushed an implementation. It's still faster than before and it also simplifies the configuration part. > At the bottom of the plugin, we can set...

I've cleaned up the commits and added code to support un-queried (non-`Mayset()`) options via the same interface. I don't really see the point of forcing all `:set`'s to go through...