<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rneovim.git/src/nvim/lua/stdlib.h, branch extregs</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(build): remove INCLUDE_GENERATED_DECLARATIONS guards</title>
<updated>2025-08-14T07:34:38+00:00</updated>
<author>
<name>bfredl</name>
<email>bjorn.linse@gmail.com</email>
</author>
<published>2025-08-03T09:16:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=442f297c633375074a88133a9b3d8c08cad58dd0'/>
<id>442f297c633375074a88133a9b3d8c08cad58dd0</id>
<content type='text'>
These are not needed after #35129 but making uncrustify still play nice
with them was a bit tricky.

Unfortunately `uncrustify --update-config-with-doc` breaks strings
with backslashes. This issue has been reported upstream,
and in the meanwhile auto-update on every single run has been disabled.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
These are not needed after #35129 but making uncrustify still play nice
with them was a bit tricky.

Unfortunately `uncrustify --update-config-with-doc` breaks strings
with backslashes. This issue has been reported upstream,
and in the meanwhile auto-update on every single run has been disabled.
</pre>
</div>
</content>
</entry>
<entry>
<title>refactor(build): don't use the preprocessor when generating headers</title>
<updated>2025-08-06T13:10:25+00:00</updated>
<author>
<name>bfredl</name>
<email>bjorn.linse@gmail.com</email>
</author>
<published>2025-08-01T10:26:52+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=79c8159f4179d47f4292da656b443ebcacd2d8bd'/>
<id>79c8159f4179d47f4292da656b443ebcacd2d8bd</id>
<content type='text'>
Using the preprocessor before generating prototypes provides some
"niceties" but the places that rely on these are pretty few.
Vastly simplifying the BUILD SYSTEM is a better trade-off.

Unbalancing { } blocks due to the preprocessor is cringe anyway (think
of the tree-sitter trees!), write these in a different way.

Add some workarounds for plattform specific features.

INCLUDE_GENERATED_DECLARATIONS flag is now technically redundant,
but will be cleaned up in a follow-up PR as it is a big mess.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Using the preprocessor before generating prototypes provides some
"niceties" but the places that rely on these are pretty few.
Vastly simplifying the BUILD SYSTEM is a better trade-off.

Unbalancing { } blocks due to the preprocessor is cringe anyway (think
of the tree-sitter trees!), write these in a different way.

Add some workarounds for plattform specific features.

INCLUDE_GENERATED_DECLARATIONS flag is now technically redundant,
but will be cleaned up in a follow-up PR as it is a big mess.
</pre>
</div>
</content>
</entry>
<entry>
<title>refactor: move Arena and ArenaMem to memory_defs.h (#26240)</title>
<updated>2023-11-27T09:21:58+00:00</updated>
<author>
<name>zeertzjq</name>
<email>zeertzjq@outlook.com</email>
</author>
<published>2023-11-27T09:21:58+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=574d25642fc9ca65b396633aeab6e2d32778b642'/>
<id>574d25642fc9ca65b396633aeab6e2d32778b642</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>refactor: replace manual header guards with #pragma once</title>
<updated>2023-11-12T21:01:28+00:00</updated>
<author>
<name>dundargoc</name>
<email>gocdundar@gmail.com</email>
</author>
<published>2023-11-10T11:23:42+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=4f8941c1a5f1ef6caa410feeb52e343db22763ce'/>
<id>4f8941c1a5f1ef6caa410feeb52e343db22763ce</id>
<content type='text'>
It is less error-prone than manually defining header guards. Pretty much
all compilers support it even if it's not part of the C standard.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It is less error-prone than manually defining header guards. Pretty much
all compilers support it even if it's not part of the C standard.
</pre>
</div>
</content>
</entry>
<entry>
<title>refactor: split executor.c into two files</title>
<updated>2021-10-26T19:04:52+00:00</updated>
<author>
<name>Dundar Göc</name>
<email>gocdundar@gmail.com</email>
</author>
<published>2021-10-23T09:46:59+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rneovim.git/commit/?id=13d331ef0de7e59ec846c47e4b0639b9e50cb06e'/>
<id>13d331ef0de7e59ec846c47e4b0639b9e50cb06e</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
