Evgeni Chasnovski

> Don't know why. I believe this all traces to the [6.2.418](https://github.com/vim/vim-history/commit/48c458fc3034f4a94b4d7c4df9abbc53daf1442d). Here is the timeline: - b66bab381c8ba71fd6e92327d1d34c6f8a65f2a7 moved the condition from 'src/getchar.c' to the current 'src/map.c'. - The previous...

Sure. I'll take a look sometime this week.

@chrisbra, I am afraid simply removing [these lines](https://github.com/vim/vim/blob/85f36d61e09b12d6f1c60201129823371daa4a84/src/map.c#L1590-L1592) breaks [this test assertion](https://github.com/vim/vim/blob/85f36d61e09b12d6f1c60201129823371daa4a84/src/testdir/test_mapping.vim#L25) with `Expected '"echo "cheese"' but got '"echo "xxx"'`. Which is understandable since the condition intended as a solution...

That part is from #15815 which was mostly documenting the current behavior (in part as a result of the use case in this issue. Yes, using `` in mappings works,...

> we could switch it, but then we would have the opposite problem: How to make sure an abbreviation is not expanded when a mapping triggers? Let's not change it...

> * when text comes from a abbreviation, the following text (whether it comes from a mapping or was typed, doesn't matter), should only expand the abbreviation if it either...

> What about url schemas, like Nix has with its `fetchTree` (and, by extension, flakes): "gitlab:some-fella/plug.nvim" for "https://gitlab.com/some-fella/plug.nvim.git"? Or will that be too much for this? The actual flexibility that...

> Unless I'm confused, that makes it impossible to use `vim.pack` to install something that a user prefers to load only sometimes. Yes, it is possible. Call `vim.pack.add()` with plugin...

> Maybe this is where I am confused. Will vim.pack uninstall packages that are present in `opt/` but no longer in a user's start-up files? If not, then I think...

> But "are not used" is now ambiguous. Some plugins "are not used (at startup)"—meaning plugins that are wanted but which users will only sometimes call on with a manual...