Doh! I moved /etc/virc (which is surely an aberrant rc filename for vim) on
the wrong server (I have 4 hops to get to the one in question). It is that.
Here's the file if you're interested (I'm going to remove it):
grahamn@gn-linux:~/remotes$ clear ; cat virc
if v:lang =~ "utf8$" || v:lang =~ "UTF-8$"
set fileencodings=ucs-bom,utf-8,latin1
endif
set nocompatible " Use Vim defaults (much better!)
set bs=indent,eol,start " allow backspacing over everything in
insert mode
"set ai " always set autoindenting on
"set backup " keep a backup file
set viminfo='20,\"50 " read/write a .viminfo file, don't store more
" than 50 lines of registers
set history=50 " keep 50 lines of command line history
set ruler " show the cursor position all the time
" Only do this part when compiled with support for autocommands
if has("autocmd")
augroup redhat
autocmd!
" In text files, always limit the width of text to 78 characters
autocmd BufRead *.txt set tw=78
" When editing a file, always jump to the last cursor position
autocmd BufReadPost *
\ if line("'\"") > 0 && line ("'\"") <= line("$") |
\ exe "normal! g'\"" |
\ endif
" don't write swapfile on most commonly used directories for NFS mounts
or USB sticks
autocmd BufNewFile,BufReadPre /media/*,/mnt/* set
directory=~/tmp,/var/tmp,/tmp
" start with spec file template
autocmd BufNewFile *.spec 0r /usr/share/vim/vimfiles/template.spec
augroup END
endif
if has("cscope") && filereadable("/usr/bin/cscope")
set csprg=/usr/bin/cscope
set csto=0
set cst
set nocsverb
" add any database in current directory
if filereadable("cscope.out")
cs add cscope.out
" else add database pointed to by environment
elseif $CSCOPE_DB != ""
cs add $CSCOPE_DB
endif
set csverb
endif
" Switch syntax highlighting on, when the terminal has colors
" Also switch on highlighting the last used search pattern.
if &t_Co > 2 || has("gui_running")
syntax on
set hlsearch
endif
filetype plugin on
if &term=="xterm"
set t_Co=8
set t_Sb=dm
set t_Sf=dm
endif
" Don't wake up system with blinking cursor:
" http://www.linuxpowertop.org/known.php
let &guicursor = &guicursor . ",a:blinkon0"
On 6 May 2014 14:01, Tim Chase <[email protected]> wrote:
> On 2014-05-06 04:18, Graham Nicholls wrote:
> > On a RHEL 6.2 server, I get odd behaviour with vim 7.2.411;
> > randomly at a frequency of about 1 in 5, entering :q! (when in
> > command mode) puts me into insert mode after adding an M and a
> > blank line.
> >
> > A subsequent :q! usually works, but sometimes does the same.
> >
> > I'm using konsole under KDE if that's of interest.
>
> It would be more helpful to know what plugins and non-standard
> settings you have. I'm going to guess that if you repeatedly try
>
> vim -u NONE ...
>
> it shouldn't give you any trouble. If it does, then there's
> something much shadier going on. If that works just fine, there's
> likely some mapping interfering with your command.
>
> I also presume that, if you type ":q!" in other programs, such as
> another text-editor or the command-shell, you have no problems
> (ruling out a flaky keyboard like the built-in one on my laptop here
> where the ZAQ1!<tab> cluster is broken).
>
> -tim
>
>
>
>
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
