Olivia (Zoe)

Hm, that is interesting. Checked with the default vimrc location, and that does indeed behave correctly. Explains why the report hasn't emerged yet I suppose; I used `-u` to start...

Hm, so `-u` fully ignores `set nocompatible` in the loaded file? How come the legacy vimscript vimrc doesn't do the same thing?

Probably. `-N` does still work to be fair, so it sounds reasonable for it to be initialization-related somehow.

Last I checked, it only ignores pairs that are prefixed with a \\. As an immediate hack, that means `'\['` as an opening pair should be fine (because escaping that...

Looked into it - there's a fundamental flaw in pair escaping that essentially disables single-byte pairs with a preceding backslash. Looking into patching it

I've (theoretically) fixed this -- you'll need to switch to my fork to use it, though (I'd merge it in, but the original maintainer is missing; there's other issues pointing...

The bugfix hasn't been tagged yet (upd.: has been tagged now) - make sure you're using the master branch and not a tagged version like the readme recommends (it's usually...

Another plugin is likely interfering with ``. What's the output of `:verbose imap `?

@MuhammadSawalhy What's the output of `:verbose imap )`? Also gonna need to see `:version`, the literal insertion of `^R` probably indicates an out-of-date vim.

Hm, weird. Not sure if nvim is to blame here, will have to try when I get home. The mapping looks generally okay though, which is annoying. There have been...