Is the LSP support in nvim better than what you can get with plugins? I’m using coc.nvim with vim and yeah it is really cool.
I didn’t know about that :term
difference. I think I prefer vim’s behavior there.
If you have :set hidden
, then the current buffer will be hidden when you open a different file, and you won’t be prompted. Without it, vim doesn’t allow hidden buffers and will discard the buffer when you open a different file (which is why it prompts you). Vim’s defaults are very odd sometimes.
Huh, that cw
behavior in vi does seem pretty jarring. Interesting, though. It makes sense why it was like that.
You can’t defederate from the bridge because it’s not going to be the only instance of the bridge. Anyone will be able to host an instance of the bridge server, just like anyone can host an instance of any fedi software. Sure, you can block
brid.gy
, but then you also have to block every other instance, too. On the mastodon instance I use, there are 45 blocked instances of Birdsite Live, a (now defunct, one way) Twitter bridge!Opting out with a hashtag technically works, but there is a character limit in the mastodon bio. It also depends on all bridges agreeing to the same hashtag.
Opt-in just makes a lot more sense, imo. It avoids different instances hosting duplicate mirrors and it avoids anyone (on bsky or fedi!) from having their posts scraped and mirrored to a different network without their knowledge.