No need to ask for permission to link for stuff like this, I made a post on public platform and anyone can share it as they see fit. Also glad I could help.
reggie
A blog of course.
vim.g.slime_default_config = {
socket_name = 'default',
target_pane = '{last}'
}
vim.g.<variable>
is the same as g:<variable>
in VimL. Assigning a dictionary is very straightforward as lua tables map to VimL dictionaries, with the exception of empty dicts where you have to use vim.empty_dict()
.
Omg, Martineski, my favorite niche internet microcelebrity replied to me!
You can wrap the call in pcall, which is a lua builtin for catching errors, which would suppress the error and let you know if the command failed.
You could for example do:
local ok, res = pcall(vim.cmd.write)
if not ok
then
vim.notify('write failed with: ' .. res)
end
There are both lua and vim functions for writing to files but I recommend to not use them in this scenario, they write to the file directly and dont trigger autocommands.
I understand your frustration with no consitent error reporting and clear api, but I guess that's the consequence of the entire history of vi and vim and trying to be backwards compatible.
I don't care what it is, it looks very fuckable.
The real reason why fmhy chose Calckey instead of Mastodon is very obviously the hot furry mascot.
vim.cmd.<command>
calls a command. So vim.cmd.write
is effectively the same as :write
, the arguments passed to the function are the same that the command would take. Check :h vim.cmd()
and for a specific command, e.g. write, you can check :h :write
.
You can call commands and vim functions from lua. To write the current buffer you can: vim.cmd.write()
. Vim functions can be called with vim.fn
.
It is completely fine to use vim functiona and not just pure lua, afaik some vim functions are not ever gonna get a lua alternative cause there is no need.
I would try using https://rss-bridge.org/bridge01/, there is a bridge that can filter feeds. You could use that and not actually filter anything so it ends up just being a proxy.
OpenSUSE
inb4 but thats a corporate distro, it is just sponsored by SUSE but is community maintained
I agree that there are not many distros that are both user friendly and not forks of something else, but I don't see it as an issue, imo there is nothing wrong with forks.