Michael Henry

You can try the below as a work-around. Using `CTRL-v`, you can insert the literal key code sequence that is generated by ``. Type the following in Vim: ```vim :map...

After looking at this for a while, it appears that the problem isn't the keycode `\e@`, but instead is the attempt to use that keycode directly for ``. As a...

Hi, Tony, Yes, Gvim works correctly when mapping `` directly (i.e., without fiddling with setting the key codes). As you imply, Gvim tends to have a better shot at getting...

As an alternative to maintaining per-terminal settings in vimrc, you might find my Fixkey plugin useful. It configures several classes of keys for a number of terminal types, allowing use...

This seems to be an issue with bashlex, e.g.: ```python In [1]: import bashlex In [2]: bashlex.parse("""gcc -DVERSION='"1.2.3.4"'""") Out[2]: [CommandNode(parts=[WordNode(parts=[] pos=(0, 3) word='gcc'), WordNode(parts=[] pos=(4, 25) word='-DVERSION=1.2.3.4')] pos=(0, 25))] ```...

All, I've been experimenting with building std from source, using both Xargo and the new Cargo `build-std` feature. Here are the steps I used on my Ubuntu workstation to get...

The `'autoread'` feature does not work out-of-the-box for both `nvim-qt` and `neovide`: - - The `'autoread'` feature does work for `nvim`'s TUI. The reason it works for the TUI is...

An ``:Ack`` invocation uses ``:grep`` under the hood. When Vim executes ``:grep``, it creates a temporary file to hold the results, runs the program, parses the temporary file to get...

@losingkeys You might like the quickfix reflector plugin: https://github.com/stefandtw/quickfix-reflector.vim It allows editing of the QuickFix window (including deletion of lines), and also a write-back of modified text in the QuickFix...

The `'autoread'` feature does not work out-of-the-box for both `nvim-qt` and `neovide`: - - The `'autoread'` feature does work for `nvim`'s TUI. The reason it works for the TUI is...