Frequently Asked Questions

These are the most common questions users ask about ViEmu/SQL, hopefully yours is answered below. If it isn't, don't hesitate to ask us by e-mail.

Most keybindings have disappeared, and they don't show in the left panel of Tools|ViEmu Settings->Keyboard
This happens especially after uninstalling ViEmu/SQL. You can force SQL Server Management Studio to reassign all default keybindings by deleting the following two files before starting it up: User.vsk and Current.vsk in C:\Documents and Settings\{username}\Application Data\Microsoft\Microsoft SQL Server\90\Tools\Shell.

ViEmu removed a keybinding I usually use, and I've tried to restore it, but it sometimes gets removed again!
Every time Management Studio is started, ViEmu scans the active keybindings for clashing keys, which it removes during the session for best vi/vim emulation. It also stores the list of removed keybindings, and uses that list to restore them every time it is deactivated (either in the Tools|ViEmu Settings page, or using Ctrl-Shift-Alt-V). Once ViEmu is activated again, it will remove the same keybindings to regain the initial state. You can modify the list of keys checked for clashes in Tools|ViEmu Settings->Keyboard.

In vim, when you enter replace mode with 'R', backspace restores the last overwritten character. ViEmu/SQL simply deletes it. I miss vim's behavior!
The problem here is that Management Studio integration requires behaving in the same way as the original editor, so there is nothing that can be done about this.

I tried [insert favorite vi/vim feature] and it doesn't work!
Please, tell us so that it can be taken into account in new versions. ViEmu/SQL is getting better every month thanks to suggestions from users. Alpha/beta versions are usually made available to customers and users who are evaluating the product (check the forums for the latest builds), with a much shorter turnaround than waiting for the next official release. Thus, if the feature you are asking for is an oversight which is simple to implement, chances are you may have it available in a short lapse of time.

Why such a product? Getting back to 70's text editing?
I guess you're not a vi/vim diehard. Granted, it's not for everyone, but for many people, once past the initial 2-3 weeks learning curve, which is steep, it becomes much more powerful and quicker than regular "arrows" style text editing. After months, your brain actually gets hardwired and it takes effort to not use it. This product is for such people (which, you can guess, includes myself). Read this if you want to know how and why I got started with vi-vim myself less than two years ago, and hopefully it will make some sense.