* Martti Kühne <mysat...@gmail.com> [20.08.2011 00:25]:
> On Fri, Aug 19, 2011 at 11:31 PM, Uli Armbruster
> <uli.armbrus...@googlemail.com> wrote:
> > My problem is, in vim the right and left arrow keys don't do anything in 
> > command mode
> 
> What locale, what keyboard setting, what terminal
> emulator/console/terminal multiplexer and what other aspect of the
> environment might be causing the error? Did you try to replicate the
> behaviour on a different machine?
> 
> mar77i

Thanks to all you so far. So it's - as I expected - a problem on my side (which 
I found while I was writing this, but still I'll post it completely)

I am german, but I have an english system, so:

% locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

and a german keyboard setting:

in my rc.conf:
KEYMAP="de"

in my xorg.conf.d/
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "XkbLayout" "de"
Option "XkbModel" "pc105"
EndSection

By the way, on tty it's the same behaviour, so it's not caused by Xorg

I use rxvt-unicode, just tried it in xterm, same behaviour.

I also reinstalled vim and vim-runtime. Actually I installed vim and replaced 
gvim, which I had installed. Nothing's changed. Then I reinstalled gvim and 
tried it with gvim, still the same.

-- la solucion --

Ok, now I found it, I completely removed gvim, so some plugins were uninstalled 
as well. Then after reinstalling vim everything's fine.

This was caused by vim-bufstat-git from the AUR. I actually don't need this, so 
I'll leave it off the system for now and file a bugreport.

An interesting part is, my mail client is mutt, which I configured to use vim 
as editor. While I was writing this mail, my problem was even solved in this 
running vim session. Weird stuff!


Thanks for your input, I was just to hasty, should have tried to figure it out 
before posting here.

Solved :)

Reply via email to