-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions (Thoughts) regarding recent changes #1213
Comments
Glad to see you are back again! |
Also can we add |
The reason why I remove |
nice! tks! |
Version confirmation
Following prerequisites
Not a user config issue
Neovim version
NVIM v0.9.5
Operating system/version
macOS 14.4.1 (23E224)
Terminal name/version
kitty 0.33.1
$TERM environment variable
kitty
Branch info
main (Default/Latest)
Fetch Preferences
SSH (use_ssh = true)
How to reproduce the issue
Sorry for not being active for a long time lol things got pretty hectic recently. I've been trying to catch up with all the changes here over the past couple of days (though not completely there yet), but I've got some questions and thoughts:
I'm curious why
sindrets/diffview.nvim
got removed? I checked Clean project plugins #1196 and refactor(plugins): iterate plugins #1198 but couldn't find any useful info (or maybe I just missed something in my speedy scroll lmao, my bad). Initially, I thought maybe there's a better alternative, but it doesn't seem like 61c817f introduced changes for that, right? I also thought about vim-fugitive (heavy user here lmao), but maybe that's not as straightforward compared to diffview.nvim?Is there a slicker way to write
_G._buf_vtext
introduced in ccd5eda? AFAIK there'svim.region()
(or in nightly,vim.getregion()
), which intuitively fetches content from the corresponding region without the need for the intermediate step (using registers). Plus, using registers might make it tricky for neovim to distinguish some control characters (check:h copy-move
).Why did we remove
gelguy/wilder.nvim
? It has some features thatcmp-cmdline
lacks (likeMan.lua
completion) and has been using APIs that have been around for some time, so it's unlikely to suddenly stop working in recent neovim releases. Personally, I feel like just because a plugin isn't actively maintained doesn't mean it's unusable, especially when it offers some irreplaceable and non-bloated functionality (though yeah, I might be a bit biased towardswilder.nvim
, sorry about that).Maybe we could think about providing a "silent install" option? I briefly mentioned my thoughts in Automatic or silent installation #1185 (comment).
It seems like we've introduced (official?) support for nightly builds in 9a15365? I'm wondering because nightly tends to have "some sort of" changes frequently, so supporting it might come with a bunch of potential small issues. And since neovim is still mostly backward compatible, installing the stable-version config for nightly builds doesn't appear to pose significant issues.
Expected behavior
1/3. Thinking of reintroducing
sindrets/diffview.nvim
(along withgelguy/wilder.nvim
).2. Rewrite
_G._buf_vtext
usingvim.region()
.4. Adding a "silent install" option.
5. Maybe we can give a heads up to nightly users that corresponding configs (e.g., branch
0.10
) are available (instead of just installing the nightly-version config), but since they're not officially supported, suggesting they try fixing issues themselves or stick to stable versions.Actual behavior
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: