<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rneovim.git/test/unit/keymap_spec.lua, branch tmp</title>
<subtitle>Neovim fork with Rahm's personal hacks.</subtitle>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/'/>
<entry>
<title>refactor: rename keymap.{c,h} to keycodes.{c,h} (#18535)</title>
<updated>2022-05-12T12:19:29+00:00</updated>
<author>
<name>zeertzjq</name>
<email>zeertzjq@outlook.com</email>
</author>
<published>2022-05-12T12:19:29+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=3a91adabda43376638e0edc80f54181258c98dea'/>
<id>3a91adabda43376638e0edc80f54181258c98dea</id>
<content type='text'>
Most code in keymap.h is for keycode definitions, while most code in
keymap.c is for the parsing and conversion of keycodes.

The name "keymap" may also make people think these two files are for
mappings, while in fact keycodes are used even when no mappings are
involved, so "keycodes" should be a better file name than "keymap".</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Most code in keymap.h is for keycode definitions, while most code in
keymap.c is for the parsing and conversion of keycodes.

The name "keymap" may also make people think these two files are for
mappings, while in fact keycodes are used even when no mappings are
involved, so "keycodes" should be a better file name than "keymap".</pre>
</div>
</content>
</entry>
<entry>
<title>vim-patch:8.2.0855: GUI tests fail because the test doesn't use a modifier</title>
<updated>2022-04-29T07:51:04+00:00</updated>
<author>
<name>zeertzjq</name>
<email>zeertzjq@outlook.com</email>
</author>
<published>2022-04-26T07:05:56+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=abe91e1efec84c47c03a69ab8a998bb16f628084'/>
<id>abe91e1efec84c47c03a69ab8a998bb16f628084</id>
<content type='text'>
Problem:    GUI tests fail because the test doesn't use a modifier.
Solution:   Add "\{xxx}" to be able to encode a modifier.
https://github.com/vim/vim/commit/ebe9d34aa07037cff2188a8dd424ee1f59cbb0bf

Change macros to enums to use them in unit tests.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Problem:    GUI tests fail because the test doesn't use a modifier.
Solution:   Add "\{xxx}" to be able to encode a modifier.
https://github.com/vim/vim/commit/ebe9d34aa07037cff2188a8dd424ee1f59cbb0bf

Change macros to enums to use them in unit tests.
</pre>
</div>
</content>
</entry>
<entry>
<title>vim-patch:8.1.2145: cannot map &lt;C-H&gt; when modifyOtherKeys is enabled</title>
<updated>2022-04-29T07:51:03+00:00</updated>
<author>
<name>zeertzjq</name>
<email>zeertzjq@outlook.com</email>
</author>
<published>2022-03-31T07:47:53+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=dde4f09f51ffaf8df5cc2a81eed935e31e1f94ba'/>
<id>dde4f09f51ffaf8df5cc2a81eed935e31e1f94ba</id>
<content type='text'>
Problem:    Cannot map &lt;C-H&gt; when modifyOtherKeys is enabled.
Solution:   Add the &lt;C-H&gt; mapping twice, both with modifier and as 0x08.  Use
            only the first one when modifyOtherKeys has been detected.
https://github.com/vim/vim/commit/459fd785e4a8d044147a3f83a5fca8748528aa84

Add REPTERM_NO_SPECIAL instead of REPTERM_SPECIAL because the meaning of
"special" is different between Vim and Nvim.
Omit seenModifyOtherKeys as Nvim supports attaching multiple UIs.
Omit tests as they send terminal codes.
Keep the behavior of API functions.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Problem:    Cannot map &lt;C-H&gt; when modifyOtherKeys is enabled.
Solution:   Add the &lt;C-H&gt; mapping twice, both with modifier and as 0x08.  Use
            only the first one when modifyOtherKeys has been detected.
https://github.com/vim/vim/commit/459fd785e4a8d044147a3f83a5fca8748528aa84

Add REPTERM_NO_SPECIAL instead of REPTERM_SPECIAL because the meaning of
"special" is different between Vim and Nvim.
Omit seenModifyOtherKeys as Nvim supports attaching multiple UIs.
Omit tests as they send terminal codes.
Keep the behavior of API functions.
</pre>
</div>
</content>
</entry>
<entry>
<title>os/input.c: parse keycodes in non-string context #7411</title>
<updated>2018-01-18T00:37:51+00:00</updated>
<author>
<name>lePerdu</name>
<email>zdpeltzer@gmail.com</email>
</author>
<published>2017-10-18T22:27:31+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=bc17ad31dccb446fc24e0f6bb3cb2149ce951ae5'/>
<id>bc17ad31dccb446fc24e0f6bb3cb2149ce951ae5</id>
<content type='text'>
cb02137dfac7 had two mistakes, of the same nature: trans_special() must
be invoked with in_string=false unless the parsing context is a VimL
string. replace_termcodes() and input_enqueue() are low-level
mechanisms where VimL strings do not exist.

keymap.c: adjust double-quote case to satisfy keymap_spec.lua

closes #7410
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
cb02137dfac7 had two mistakes, of the same nature: trans_special() must
be invoked with in_string=false unless the parsing context is a VimL
string. replace_termcodes() and input_enqueue() are low-level
mechanisms where VimL strings do not exist.

keymap.c: adjust double-quote case to satisfy keymap_spec.lua

closes #7410
</pre>
</div>
</content>
</entry>
</feed>
