On 27/08/08 06:05, Bill McCarthy wrote:
> On Tue 26-Aug-08 7:25pm -0600, Tony Mechelynck wrote:
>
>> ----------------------------------
>> Ah! I found them !!!!!!!!!!!!!!!!!
>> ----------------------------------
>> see ":help dos-standard-mappings"
>
> Thanks Tony! I've revised my _vimrc correction to work fine
> for Vim as well as Gvim:
>
> " Remove the not useful select mode versions
> sunmap<C-X>
> if has("GUI")
> sunmap<C-Del>
> sunmap<S-Del>
> sunmap<C-Insert>
> sunmap<S-Insert>
> else
> sunmap<M-N><M-T>
> sunmap<M-N><M-U>
> sunmap<M-N><M-W>
> sunmap<M-N><M-X>
> " and these strange mappings
> unmap!<C-End>
> unmap!<C-Home>
> unmap<C-End>
> unmap<C-Home>
> endif
>
For Windows this is OK (I think), but remember (just in case) that on
Unix/Linux a single executable can work either in Console mode or GUI
mode. There, has('gui') and has('gui_running') are different:
has('gui')
GUI capability is compiled-in
has('gui_running')
we are in the GUI, or about to start it
In addition, on Unix/Linux you can start a GUI-enabled Vim in Console
mode and later start the GUI with ":gui". In that case your vimrc will
already have been sourced with !has('gui_running'), but sourcing the
gvimrc, triggering the GUIEnter event starting the GUI, and possibly
forking from the console terminal, will all happen as a result of the
":gui" command (and with has('gui_running') on). (Personally I don't use
that copmmand, but some other people sometimes do.)
In all GUI versions, the 'term' setting is set to builtin_gui when
starting the GUI. The termcap settings (including e.g. the visualbell
screen code) are then changed and maybe also the "default Dos/Windows
mappings". In that case undoing the default GUI mappings in the vimrc
could be too soon, in that case you can use either a gvimrc or a
GUIEnter autocommand.
Best regards,
Tony.
--
This is for all ill-treated fellows
Unborn and unbegot,
For them to read when they're in trouble
And I am not.
-- A. E. Housman
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
