lacygoill

> But ideally, "undefined variable: tabs_len" or the like would be best, but I'm guessing there may be a reason it doesn't do that already. The difference between `tabs_len` and...

How about we append `(missing var?)` at the end of the message? Before: E1144: Command "tabs" is not followed by white space: tabs_len = 2 After: E1144: Command "tabs" is...

That's what we do in `E1100`: The previous patch would make `E1144` inconsistent with `E1100`. New patch to make it consistent: ```diff diff --git a/src/errors.h b/src/errors.h index 8aad956d9..78ccda660 100644 ---...

Maybe we should add the `or` conjunction to make it clear that it's another possible cause for the error (and not further info about the previous cause): ```diff diff --git...

- Which terminal? - Which `$TERM` - Which OS? - Which Vim version? Try to reduce your vimrc as much as possible, and try to reproduce on master. BTW, your...

> The last 8.1 patch 8.1.2424 was committed the 13 December of 2019. The same day, the first 8.2 patch 8.2.0001 was committed. Actually, 8.1.2424 was committed on December 11,...

There were differences in performance between eval strings and lambdas, but those differences changed over time. Right now, on my machine, I don't see a significant difference: 0.656 seconds to...

Try to profile the C code: $ make clean && make distclean $ sed -i '/#PROFILE_CFLAGS = -pg -g -DWE_ARE_PROFILING/s/^#// ; /#PROFILE_LIBS = -pg -no-pie/s/^#//' src/Makefile $ make $ ./src/vim...

If you do several tests, or if your Vim working directory already contains modifications, make sure to start from a clean state: $ git reset --hard $(git rev-parse HEAD) Also,...

> What ends up being more efficient is very hard to predict. For this specific code, both syntaxes seem to give similar results (see the previous comments, [here](https://github.com/vim/vim/issues/11163#issuecomment-1250771580) and [here](https://github.com/vim/vim/issues/11163#issuecomment-1250812031))....