Hello gandalf,

You are right to complain. There are several issues here conflating to create a horrible user experience. Let's try to address'em as possible.

1) For Ctrl-F (or any other keypress for that matter) to get through to ViEmu, it's necessary that it is *NOT* mapped to any VS keybinding in Tools|Options|Keyboard. This is inherent to VS's architecture, I don't like the design, but that's how it is: VS's main message pump examines keypresses for VS-bindings, and if matching, the keypress is never delivered, but converted to an OLE command. This is why ViEmu removes clashing keybindings the first time it runs (it saves them for dynamic restoring/removal when toggling ViEmu on and off).

So, what you have to do to make Ctrl-F scroll, is to remove its Tools|Options|Keyboard binding(s). If you want to go fancy and make it "come back" when toggling ViEmu off, the process is just a bit more involved (using the ViEmu config dialog). This is described in the docs, let me know and I'll be happy to elaborate more if necessary.

2) There is a VS macro that can be run to list all active keybindings, someone posted it on their blog. Here it is:

-------
Imports EnvDTE
Imports System.Diagnostics

Public Module KeyboardShortcuts

    Sub ListKeyboardShortcuts()
        Dim i As Integer
        Dim j As Integer
        Dim pane As OutputWindowPane = Utilities.GetOutputWindowPane("Commands")
        Dim keys As System.Array

        pane.Clear()
        pane.OutputString("<font face=arial>")
        pane.OutputString("<table border=1 cellspacing=0 cellpadding=2 bgcolor=f0f0ff>" + Chr(10))
        pane.OutputString("<tr><th colspan=2 bgcolor=d0d0e0>Keyboard Mappings</th></tr>" + Chr(10))
        pane.OutputString("<tr><th bgcolor=e0e0f0>Action</th>")
        pane.OutputString("<th bgcolor=e0e0f0>Key</th></tr>" + Chr(10))

        For i = 1 To DTE.Commands.Count
            keys = DTE.Commands.Item(i).Bindings
            If keys.Length > 0 Then
                pane.OutputString("<tr>")

                'DTE.Commands.Item(i).Name() is sometimes blank.
                'We will print an m-dash in this case, as printing a blank table cell is visually
                'misleading, as such a cell has no borders, making it appear to be attached to
                'another cell.
                If DTE.Commands.Item(i).Name() <> "" Then
                    pane.OutputString("<td valign=top>" + DTE.Commands.Item(i).Name())
                Else
                    pane.OutputString("<td><center>&mdash;</center>")
                End If

                pane.OutputString("</td><td>")
                For j = 0 To keys.Length - 1
                    If j > 0 Then
                        pane.OutputString("<br/>")
                    End If
                    pane.OutputString(keys(j))
                Next
                pane.OutputString("</td></tr>" + Chr(10))
            End If
        Next

        pane.OutputString("</table></font>")

    End Sub

End Module
-------

Not as nice as what you show, but it will work. The VS keybinding system is also ugly in some other aspects, with commands without names and the like, but hopefully the output from the above macro will be an improvement.

3) I agree Tools|Options|Keyboard is bad. If you want to see what command a keypress maps too, you can go to the "current keybinding" edit box, press the combination you want to check (annoyingly, it doesn't work for simple keypresses like "Return", "Backspace", etc...), and you will be able to check the commands it's bound to.

4) My own "ViEmu keyboard config" dialog is pretty sucky too. I will make it bigger as a first solution (I'll post back here). The mid- to long-term solution is a better keypress-interception mechanism which won't require removing VS keybindings, this is half-implemented and based on ViEmu/Word&Outlook's mechanism. Hopefully that will make everything simpler and clearer the day it's ready.

Apologies for the horrible user-experience, and let me know if I can help out with anything else!

  -- Jon

^F and ^B now go forward and backward as expected with ViEmu.  The clashing ^B must have been saved and removed, though I don't see it in Saved keybindings:

Edit.MakeLowercase=Text Editor::Ctrl+U
Edit.GotoBrace=Text Editor::Ctrl+]
Edit.SelectCurrentWord=Text Editor::Ctrl+W
Edit.ViewWhiteSpace=Text Editor::Ctrl+R, Ctrl+W
Edit.ToggleWordWrap=Text Editor::Ctrl+E, Ctrl+W
Edit.IncrementalSearch=Text Editor::Ctrl+I
Refactor.ExtractMethod=Global::Ctrl+R, Ctrl+M
Refactor.ExtractInterface=Global::Ctrl+R, Ctrl+I
Refactor.PromoteLocalVariable=Global::Ctrl+R, Ctrl+P
Refactor.RemoveParameters=Global::Ctrl+R, Ctrl+V
File.Print=Global::Ctrl+P
Edit.Redo=Global::Ctrl+Y||Global::Shift+Alt+Bkspce||Global::Ctrl+Shift+Z
Edit.Find=Global::Ctrl+F

They *replace* the current saved keybindings.  Oh well....   ;-)  Why turn off ViEmu anyway?

Following from my last post...

Worse yet, uninstalling ViEmu fails to restore the key bindings that it removed. Ugh.

Jon -- No outstanding issues for me on this thread.  VS keys are set up for ViEmu.  ;-)