-
Notifications
You must be signed in to change notification settings - Fork 283
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
Sidebar no refresh #3399
Comments
Hi @Amparose , Thanks for logging the issue. I actually just merged a PR earlier this week to enable auto-refresh via libuv file system watchers here: #3365 It's turned off by default, just to get some more testing around it - but you can enable it on nightly builds with:
in your configuration. Would be great to see if that fixes the refresh/reload issue for you!
Past auto-refresh, what other features are you looking for? There's a few things I'm tracking:
Are there any other things missing that we should track? |
Drag & drop moving of files / folders would also be nice 😃 |
Yeah! Along with that and coming from Nova/VSCode/Sublime, I ran into these unmet expectations/confusions:
I would hope that these could have keyboard controls as well like the origami feature in Sublime.
I'm just getting into "building my first Vim" in the last few days and only purchased/installed Onivim today, so I may not be aware of all the conventions to suggest correctly, but here are a few things that occurred to me:
EDIT: That new nightly seems to shows changes made in an open file from another app. |
Fixes #3399 - enable refresh in file explorer by default
I understand that features like rename and move are on the way for the sidebar so I jumped into a terminal to rename a file. In Onvim the sidebar does not reflect this change without closing/reopening it. Also, I just tested touching a txt file (perhaps all new files) and it doesn't show up in the sidebar even after show/hide.
CTRL p
does show recent changes and new files so perhaps the polling is available.The current Onivim sidebar is pretty useless at the moment. Hoping that it is on the roadmap to make it functional.
The text was updated successfully, but these errors were encountered: