On Dec 22, 12:32 pm, BrianP <[email protected]> wrote:
> Hi,
> When installing gvim72.exe on windoz xp, the cut (^x), copy (^c),
> select_all (^a) and paste (^v) functions all work well. And the shift-
> arrow-keys select areas of text. And, searches highlight all
> occurrences of the target which is extremely handy for source code
> editing.
>
> On Linux, these keys are all set to their "classic", 1978 vintage,
> useless functions.
>
First, while you may certainly prefer the customary Windows-style
bindings, there are many many many people on this list that certainly
prefer the "classic" functions which are certainly not useless at all.
They are just different. It would seem from your description that you
prefer to work in "insert mode" and rarely if ever leave it. This is
not how most active posters to this list operate, but we can certainly
help you do what you want. Just don't dismiss the "classic" way as
"useless." It's just different.
> How can I get the efficient, win32 behavior on Ubuntu Linux?
>
> I have tried putting the following lines in my ~/.gvimrc file with no
> effect:
I don't know if this would cause the issue, but these lines are more
appropriately placed in the ~/.vimrc file, not the ~/.gvimrc file.
The .gvimrc file is meant for GUI-only customizations, whereas .vimrc
affects any form of Vim you launch. Additionally, the .vimrc is one of
the first things loaded by Vim, whereas the .gvimrc is one of the
last. See :help startup for details.
> behave mswin
> source /usr/share/vim/vim71/mswin.vim
>
I think this should do it, really...what is the output of :scriptnames
once Vim is loaded? It is probably pretty long, so this should help
paste it efficiently:
:redir @+
:scriptnames
:redir END
Then, the output will be in your clipboard and you can paste it
wherever you want.
> What am I missing here? And, I Cream is too dumbed down.
>
I would agree, but it does serve a purpose. If you want a customary
"point-and-click" interface, and don't plan to use Vim to its full
modal editing extensible keyboard-controlled potential, then Cream is
a good thing, but I would question whether Vim is the appropriate tool
at all in that case.
> Thank you,
> BrianP
>
> r...@godzilla2:/home/brianp# cat ~brianp/.gvimrc
> set nocompatible
This certainly needs to be set in the .vimrc and not the .gvimrc,
although just HAVING a .vimrc automatically does this.
> set bs=2
> set backupdir=/tera/tmp/vim
> set directory=/tera/tmp/vim
> set shiftwidth=4
> set tabstop=4
> set visualbell
> set autoindent
>
> behave mswin
The rest should be fine in the .gvimrc as far as I know, but it
certainly is more appropriately placed in the .vimrc.
> source /usr/share/vim/vim71/mswin.vim
You said you were installing Vim 7.2, but your path indicates Vim 7.1.
You'll probably want to update your path, but instead of using an
explicit path, try the $VIMRUNTIME variable so you don't forget after
the next upgrade. $VIMRUNTIME contains everything up to the vim72 in
the path.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
