<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rneovim.git/src/nvim/lua/executor.c, branch floattitle</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>fix(lua): fix architecture-dependent behavior in usercmd "reg" (#20384)</title>
<updated>2022-09-28T10:27:59+00:00</updated>
<author>
<name>zeertzjq</name>
<email>zeertzjq@outlook.com</email>
</author>
<published>2022-09-28T10:27:59+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=35e2c4a2edd28f72c48c70530c5486365c2502a4'/>
<id>35e2c4a2edd28f72c48c70530c5486365c2502a4</id>
<content type='text'>
I don't think using an integer as a NUL-terminated string can work on
big-endian systems, at least.

This is also not tested. Add a test.

Also fix a mistake in the docs of nvim_parse_cmd.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I don't think using an integer as a NUL-terminated string can work on
big-endian systems, at least.

This is also not tested. Add a test.

Also fix a mistake in the docs of nvim_parse_cmd.</pre>
</div>
</content>
</entry>
<entry>
<title>fix(redraw): avoid unnecessary redraws and glitches with floats+messages</title>
<updated>2022-09-22T08:36:23+00:00</updated>
<author>
<name>bfredl</name>
<email>bjorn.linse@gmail.com</email>
</author>
<published>2022-09-16T17:21:32+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=00cfc1dcebd1c81dd0d8c111740782e86cf2e385'/>
<id>00cfc1dcebd1c81dd0d8c111740782e86cf2e385</id>
<content type='text'>
fixes #20106
fixes #20229
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
fixes #20106
fixes #20229
</pre>
</div>
</content>
</entry>
<entry>
<title>vim-patch:8.1.0941: macros for MS-Windows are inconsistent (#20215)</title>
<updated>2022-09-18T01:17:15+00:00</updated>
<author>
<name>dundargoc</name>
<email>33953936+dundargoc@users.noreply.github.com</email>
</author>
<published>2022-09-18T01:17:15+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=6d557e324fd4223fff3279a0112f40431c540163'/>
<id>6d557e324fd4223fff3279a0112f40431c540163</id>
<content type='text'>
Problem:    Macros for MS-Windows are inconsistent, using "32", "3264 and
            others.
Solution:   Use MSWIN for all MS-Windows builds.  Use FEAT_GUI_MSWIN for the
            GUI build. (Hirohito Higashi, closes vim/vim#3932)
https://github.com/vim/vim/commit/4f97475d326c2773a78561fb874e4f23c25cbcd9</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Problem:    Macros for MS-Windows are inconsistent, using "32", "3264 and
            others.
Solution:   Use MSWIN for all MS-Windows builds.  Use FEAT_GUI_MSWIN for the
            GUI build. (Hirohito Higashi, closes vim/vim#3932)
https://github.com/vim/vim/commit/4f97475d326c2773a78561fb874e4f23c25cbcd9</pre>
</div>
</content>
</entry>
<entry>
<title>vim-patch:8.2.3796: the funcexe_T struct members are not named consistently (#20214)</title>
<updated>2022-09-16T09:31:42+00:00</updated>
<author>
<name>zeertzjq</name>
<email>zeertzjq@outlook.com</email>
</author>
<published>2022-09-16T09:31:42+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=3dda52d860eb4937127693d4660db18305069370'/>
<id>3dda52d860eb4937127693d4660db18305069370</id>
<content type='text'>
Problem:    The funcexe_T struct members are not named consistently.
Solution:   Prefix "fe_" to all the members.
https://github.com/vim/vim/commit/851f86b951cdd67ad9cf3149e46169d1375c8d82

Omit fe_check_type: always NULL in legacy Vim script.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Problem:    The funcexe_T struct members are not named consistently.
Solution:   Prefix "fe_" to all the members.
https://github.com/vim/vim/commit/851f86b951cdd67ad9cf3149e46169d1375c8d82

Omit fe_check_type: always NULL in legacy Vim script.</pre>
</div>
</content>
</entry>
<entry>
<title>vim-patch:8.2.0067: ERROR_UNKNOWN clashes on some systems (#20212)</title>
<updated>2022-09-16T08:37:37+00:00</updated>
<author>
<name>zeertzjq</name>
<email>zeertzjq@outlook.com</email>
</author>
<published>2022-09-16T08:37:37+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=b98de0e0e5df96cadbac9222ddb1caa463cea2f0'/>
<id>b98de0e0e5df96cadbac9222ddb1caa463cea2f0</id>
<content type='text'>
Problem:    ERROR_UNKNOWN clashes on some systems.
Solution:   Rename ERROR_ to FCERR_. (Ola Söder, closes vim/vim#5415)
https://github.com/vim/vim/commit/ef140544f6703a7a4c0f6a15f610508ed6b09e89

Remove ERROR_BOTH which was removed from Vim in patch 7.4.1582.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Problem:    ERROR_UNKNOWN clashes on some systems.
Solution:   Rename ERROR_ to FCERR_. (Ola Söder, closes vim/vim#5415)
https://github.com/vim/vim/commit/ef140544f6703a7a4c0f6a15f610508ed6b09e89

Remove ERROR_BOTH which was removed from Vim in patch 7.4.1582.</pre>
</div>
</content>
</entry>
<entry>
<title>refactor: replace char_u with char</title>
<updated>2022-09-11T11:28:59+00:00</updated>
<author>
<name>Dundar Göc</name>
<email>gocdundar@gmail.com</email>
</author>
<published>2022-08-26T21:11:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=3ff46544c9872b4161fd098569c30b55fe3abd36'/>
<id>3ff46544c9872b4161fd098569c30b55fe3abd36</id>
<content type='text'>
Work on https://github.com/neovim/neovim/issues/459
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Work on https://github.com/neovim/neovim/issues/459
</pre>
</div>
</content>
</entry>
<entry>
<title>refactor: replace char_u with char</title>
<updated>2022-09-09T19:02:42+00:00</updated>
<author>
<name>Dundar Göc</name>
<email>gocdundar@gmail.com</email>
</author>
<published>2022-08-26T21:11:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=c5322e752e9e568de907f7a1ef733bbfe342140c'/>
<id>c5322e752e9e568de907f7a1ef733bbfe342140c</id>
<content type='text'>
Work on https://github.com/neovim/neovim/issues/459
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Work on https://github.com/neovim/neovim/issues/459
</pre>
</div>
</content>
</entry>
<entry>
<title>refactor(typval): change FC_CFUNC abstraction into FC_LUAREF</title>
<updated>2022-09-06T22:52:58+00:00</updated>
<author>
<name>bfredl</name>
<email>bjorn.linse@gmail.com</email>
</author>
<published>2022-09-06T20:23:54+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=db9b8b08e74ae8cfb08960eca0a7273538ebcdf1'/>
<id>db9b8b08e74ae8cfb08960eca0a7273538ebcdf1</id>
<content type='text'>
"cfuncs" was only ever used to wrap luarefs. As vim8script is
finished and will not be developed further, support for "cfuncs"
for other usecases are not planned. This abstraction was immediately
broken anyway in order to get luarefs out of userfuncs again.

Even if a new kind of userfunc needs to be invented in the future,
likely just extending the FC_... flag union directy, instead of
invoking unnecessary heap object and c function pointer indirection,
will be a more straightforward design pattern.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
"cfuncs" was only ever used to wrap luarefs. As vim8script is
finished and will not be developed further, support for "cfuncs"
for other usecases are not planned. This abstraction was immediately
broken anyway in order to get luarefs out of userfuncs again.

Even if a new kind of userfunc needs to be invented in the future,
likely just extending the FC_... flag union directy, instead of
invoking unnecessary heap object and c function pointer indirection,
will be a more straightforward design pattern.
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(api)!: correctly deal with number before :tab</title>
<updated>2022-09-02T14:28:57+00:00</updated>
<author>
<name>zeertzjq</name>
<email>zeertzjq@outlook.com</email>
</author>
<published>2022-09-01T10:46:34+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=1ef7720567b08caec0c077605fb2a01a9d6eafbc'/>
<id>1ef7720567b08caec0c077605fb2a01a9d6eafbc</id>
<content type='text'>
Now nvim_parse_cmd and nvim_create_user_command use a "tab" value which
is the same as the number passed before :tab modifier instead of the
number plus 1, and "tab" value is -1 if :tab modifier is not used.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Now nvim_parse_cmd and nvim_create_user_command use a "tab" value which
is the same as the number passed before :tab modifier instead of the
number plus 1, and "tab" value is -1 if :tab modifier is not used.
</pre>
</div>
</content>
</entry>
<entry>
<title>feat(api): add support for :horizontal modifier</title>
<updated>2022-09-01T12:53:43+00:00</updated>
<author>
<name>zeertzjq</name>
<email>zeertzjq@outlook.com</email>
</author>
<published>2022-09-01T12:32:59+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=689f5d604e59eba1ddab6f91b458a8163dc6629d'/>
<id>689f5d604e59eba1ddab6f91b458a8163dc6629d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
