-
Notifications
You must be signed in to change notification settings - Fork 7
Quirks
Vidar doesn't like to open additional windows. This means that it's not going to pop up new windows for simple things like opening a file.
Instead, commands (like open-file) will communicate with you in a small box at the bottom of the editor. This is designed to stay single-line most of the time, although we haven't ruled out expanding it for some things.
Vidar is intended to be, above all else, discoverable. We've tried to make it very difficult for a command to exist without key bindings or a menu entry. But since basically all of the functionality is bound to the editor in the same way, we have very little control over how cluttered the menus get. We also intentionally list all key bindings associated with a command directly in the menu, so it can be hard to read. We'd like to clean this up (with cleaner UI elements for the key bindings), but it's a lower priority right now.
Vidar, being a relatively young editor that began mostly as a hobby project, has some rough spots. Many of these come from decisions made early on that seemed reasonable at the time, but are now difficult to remove.
Plugins are extremely particular about being built with the same version of common dependencies and sometimes won't load. This is being worked on upstream.
- Find will place a cursor at every location. This is often very useful, but when it's annoying, it's extremely annoying.
- There's no way to go back to a previous location. This is particularly annoying when you use the godef plugin to go to a definition, then need to manually go back to where you were at before.
- History (undo/redo) has been buggy. I think we've finally fixed the last few issues, but no promises.
- There's no prompt on quit if you have unsaved changes.
- If you have unsaved changes and the file changes on disk, you won't be able to save. You'll need to select all, copy, re-open the file, select all, paste.
- Sometimes the file watch process just ... doesn't quite get things right, when a file changes on disk. usually, it should pick up the changes and present the updates to you (assuming you don't have unsaved changes), but sometimes it processes the file as if it's empty or just misses an event entirely.