regsvr32 visvile.dll
Tools
Customize...
Add-Ins and Macro Files
That's it. Now, every time Developer Studio is invoked, visvile.dll is automatically loaded as an add-in.
| Option Name | Explanation |
|---|---|
| Add-in enabled | VisVile causes winvile to open any new or existing _text_ document accessed by DevStudio, provided that the default editor doesn't already have that document open (see next option). |
| Close DevStudio copy of text document | VisVile closes DevStudio's copy of an open text document after winvile has opened its copy. This feature keeps DevStudio from issuing a warning message each time a project file is modified by an external editor. If unchecked, winvile and the DevStudio text editor co-exist side by side. But see the Caveats section below. |
| CWD set from opened document's path | Winvile's current working directory is set to match the path of any document opened by VisVile. |
| Write all modified buffers to disk prior to build |
VisVile forces winvile to flush all modified buffers to
disk before a DevStudio build begins. Note that DevStudio
(v5, at least) decides which files must be compiled _prior_
to notifying VisVile of an imminent build. This is arguably
a DevStudio (v5) bug and it does diminish the usefulness of
this option.
One workaround is to press the build accelerator key (F7) twice for each build. The first key press builds whatever files are out-of-date before modified winvile buffers are written to disk. The second key press forces DevStudio to re-examine its dependencies and build everything affected by the last winvile buffer flush. Another workaround is to become accustomed to typing :ww within winvile prior to starting a DevStudio build. |
| Build log -> errbuf if build reports errs/warning | Assuming DevStudio has been configured to create an error log (refer to the Tools->Customize->Build dialog box), then when the current DevStudio build reports errors or warnings, VisVile causes winvile to use the build log as its error buffer. In this configuration, the source code associated with each error/warning message may be directly accessed by simply typing ^X-^X. For a complete description of ^X-^X, browse vile's help and search for the string "error finder". |
| Redirect selected Winvile keys to DevStudio | Winvile redirects keystrokes specified in the "redirect-keys" mode to DevStudio. This option permits, for example, a single winvile keystroke to start a DevStudio build, execute the target application, or initiate application debugging. More will be said about this option near the end of this document. |
When VisVile is enabled, any operation that causes DevStudio to open a text file will instead/also cause winvile to open that file. Note too that repeatedly pressing the F4 key within DevStudio following a failed build causes winvile to be positioned at the source code line(s) triggering error and/or warning messages. However, _each_ error or warning message accessed via the F4 key requires a manual switch between winvile and DevStudio. For that reason, the "Build log -> errbuf..." option is much more convenient (no switching required).
The first icon, bound to command name "VisVileConfigCmd", configures VisVile. The second and third icons provide shortcuts for enabling and disabling VisVile. Note that it makes sense to disable VisVile before debugging an application (otherwise, the debugger pops up winvile whenever a breakpoint is taken). These icons are bound to command names "VisVileEnableCmd" and "VisVileDisableCmd", respectively.
The fourth icon, bound to command name "VisVileOpenDocCmd", forces winvile to unconditionally open the text document currently visible in the default text editor. This icon is often useful when VisVile is disabled.
Use this menu hierarchy:
Tools
Customize...
Keyboard (category Add-ins)
to assign DevStudio keyboard shortcuts to any of the command names mentioned in the previous section of this document.
+ DevStudio sends VisVile a "document opened" event _only_ if the affected document is not currently open in the default editor. Keep this fact in mind when configuring the "Close DevStudio copy of text document" option. This restriction does not apply to the fourth toolbar icon. + It makes sense to disable VisVile before debugging an application (otherwise, the debugger pops up winvile whenever a breakpoint is taken).
Initially, VisVile was created so that various DevStudio events caused winvile to execute text editing commands on behalf of the IDE. In other words, DevStudio controlled winvile. But given the rich interprocess communication mechanisms available in the Win32 environment, it became obvious that once DevStudio established an OLE connection with winvile, the editor could turn the tables and manipulate its OLE client :-) .
To that end, when winvile is compiled as an OLE Automation server, a new mode called "redirect-keys" is available. This mode specifies a list of keystrokes that are to be redirected to DevStudio. The list must be in the following format:
<keyspec>,...
where
<virt_key>:[<modifier>...]:[<action>...]
and
| <virt_key> | :== virtual keycode macro name sans "VK_". | Refer to the table near the end of this document for a list of keycodes that may be redirected. |
| <modifier> | :== S|C|A <-- | mnemonics for shift, control, alt |
| <action> | :== <flush>|<switch>|<sync> | |
| <Flush> | :== F <-- | flush all modified buffers to disk prior to redirecting key |
| <Switch> | :== S <-- | switch focus to redirected window prior to redirecting key |
| <sYnc> | :== Y <-- | synchronize current buffer (at its current line) within the DevStudio editor. Very useful when setting breakpoints. |
F5::S,F10::S,F11::S,F7::F,F5:C:,F9::Y
which can be translated using this table:
| KeyStoke | Action | Standard DevStudio ShortCut Semantics |
|---|---|---|
| F5 | Switch Focus | Run program under debugger |
| F10 | Switch Focus | Step over |
| F11 | Switch Focus | Step into |
| F7 | Flush buffers | Build application |
| Ctrl+F5 | <none> | Execute application |
| F9 | Sync buffer | Set/Remove breakpoint at DevStudio's current file location. |
We're almost set. For example, we can now start the debugger from winvile by simply pressing F5. Or, we might use winvile to position a source file at a desired breakpoint location and then press F9 to actually set the breakpoint in DevStudio's debugger. Neat. But wouldn't it be great if we could disable VisVile before starting the debugger so that breakpoints don't cause DevStudio to switch focus back to winvile? This is possible, but requires an assist from a small macro (written in Visual Basic). Included with the VisVile source distribution is a macro file called VisVile.dsm that includes assists for the redirected F5, F7, F9, F10, and F11 keys. The F5, F9, F10, and F11 macros simply disable VisVile prior to executing DevStudio's DebugGo, DebugToggleBreakpoint, DebugStepOver, and DebugStepInto commands, respectively. The F7 macro is a bit more complicated, but each of its actions are documented. Notice that VisVile.dsm doesn't include assist macros for Ctrl+F5, which makes sense, because target application execution does not require disabling VisVile.
Our final configuration task, then, is to modify DevStudio so that it executes Visvile.dsm's macros when the F5, F7, F9, F10, and F11 keys are pressed. We want control flow established like so (using the F10 key as an example):
Winvile User Presses F10
||
\/
DevStudio Message Pump
||
\/
Visvile.dsm's F10 Macro Executed
||
\/
VisVile Disabled
||
\/
DevStudio's DebugStepOver Command Executed
To achieve the desired objective, follow this recipe:
Tools
Customize...
Keyboard
Category
Macros
As a side effect of this sequence, the standard DevStudio F10 shortcut (available from the Debug Menu) will be deleted. Finally, in the same dialog box context, use the "Editor" drop-down box to select "Text" and again enter F10 as a new shortcut key (and don't forget to click the Assign button).
Repeat the last step for the F5, F7, F9, and F11 macros.
At this point it's probably a good idea to close DevStudio and re-invoke. After checking to ensure that VisVile.dll and VisVile.dsm are still installed as add-ins and also ensuring that your new shortcuts are in place, test the winvile redirection feature as follows:
If nothing happens when the F7 key is pressed, chances are good that DevStudio was not configured to direct the F7 key to the F7 assist macro for both the "Main" and "Text" editors.
BACK /* backspace */
TAB
PAUSE
SPACE
PRIOR
NEXT
END
HOME
LEFT
UP
RIGHT
DOWN
SNAPSHOT /* print screen */
INSERT
DELETE
0-9 /* taken from VK_0, VK_1, etc. */
A-Z /* taken from VK_A, VK_B, etc. */
APPS /* properties key (Win95 kybd) */
MULTIPLY /* keypad */
ADD /* keypad */
SUBTRACT /* keypad */
DECIMAL /* keypad */
DIVIDE /* keypad */
F1-F24 /* taken from VK_F1, VK_F2, etc. */
NUMLOCK
SCROLL
Unique to VisVile:
Unique to VisVim:
Copyright © 1998-2002 Clark Morgan
VisVile is based upon VisVim, written by Heiko Erhardt (Copyright © 1997 Heiko Erhardt). VisVim is based upon VisEmacs, written by Christopher Payne (Copyright © Christopher Payne 1997).
VisVile is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version.
VisVile is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.