okay so:

• have a libnvim.h or whatever file with a bunch of ui_event_name_yourmom(..) function declarations
• include this file in main.c or wherever but also include another header that actually defines these functions, so no issues on the neovim binary side of things
• then when the static library is built, since you won't be including the header that implements these functions on the neovim side, it will only compile when you include that header if you also include a header defining the symbols, or you define them in the file you include it with

that all correct?

okay so:

• have a libnvim.h or whatever file with a bunch of ui_event_name_yourmom(..) function declarations
• include this file in main.c or wherever but also include another header that actually defines these functions, so no issues on the neovim binary side of things
• then when the static library is built, since you as a user of libnvim won't be including the header that implements these functions on the neovim side, it will only compile when you include that header if you also include a header defining the symbols, or you define them in the file you include it with

that all correct?

okay so:

• have a libnvim.h or whatever file with a bunch of ui_event_name_yourmom(..) function declarations
• include this file in main.c or wherever but also include another header that actually defines these functions, so no issues on the neovim binary side of things
• then when the static library is built, since you as a user of libnvim won't be including the header that implements these functions on the neovim side, it will only compile when you include that libnvim.h header if you also include a header defining the symbols, or you define them in the file you include it with

that all correct?

okay so:

• have a libnvim.h or whatever file with a bunch of ui_event_name_yourmom(..) function declarations
• include this file in main.c or wherever but also include another header that actually defines these functions, so no issues on the neovim binary side of things
• then when the static library is built, since you as a user of libnvim won't be including the header that implements these functions on the neovim side, it will only compile when you include that libnvim.h header if you also include a header defining the handlers in your own project, or you define them in the file you include it with

that all correct?

In reply to @moonglade:matrix.org
Seems like vim-go uses noshellslash even for Linux

In reply to @zeertzjq:matrix.org
Yes, did you forget by comment?

Those are:

{
  "aleph",
  "browsedir",
  "completeslash",
  "guioptions",
  "guitablabel",
  "guitabtooltip",
  "imcmdline",
  "imdisable",
  "mouseshape",
  "opendevice",
  "pastetoggle",
  "shellslash",
  "termencoding",
}

In reply to @echasnovski:matrix.org
They did.

Here is a script for future reference:

_G.option_errors = {}
for name, info in pairs(vim.api.nvim_get_all_options_info()) do
  local value_source = ({ global = 'go', win = 'wo', buf = 'bo' })[info.scope]
  local errors = pcall(function() return vim[value_source][name] end)
  if not errors then table.insert(_G.option_errors, name) end
end
table.sort(_G.option_errors)
print(vim.inspect(_G.option_errors))

In reply to @echasnovski:matrix.org
Now they don't error (which is fine, I guess), but they return a not consistent values.
vim.o.aleph returns 224 (which is its Vim default), but vim.o.browsedir returns empty string while "last" is its default Vim value.