Your message dated Fri, 29 Sep 2006 10:41:19 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390151: vim-ruby doesn't support cursor arrows in insert
mode
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: vim-ruby
Version: 1:7.0-094+1
Severity: normal
Hi,
Since vim7 coming out, seems that the cursor arrows key works strange. I
have no problem in command mode, but in insert mode they spit me out
this chars:
A for the up key
B for the down key
C for the right key
D for the left key
instead of moving the cursor.
I always test this with "vim -u NONE" start command. I tested different
flavor of LANG variables (C, en_US...), but no luck.
I also tested with xterm (I usually use aterm, and it has rxvt term
style), also without any luck.
This problem seems relative just at the vim-ruby package. The "normal"
vim doesn't has this problem.
Thank you.
-- System Information:
Debian Release: testing/unstable
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500,
'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages vim-ruby depends on:
ii libatk1.0-0 1.12.2-1 The ATK accessibility toolkit
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libcairo2 1.2.4-1 The Cairo 2D vector graphics libra
ii libfontconfig1 2.4.1-2 generic font configuration library
ii libglib2.0-0 2.12.3-2 The GLib library of C routines
ii libgpmg1 1.19.6-22 General Purpose Mouse - shared lib
ii libgtk2.0-0 2.8.18-1 The GTK+ graphical user interface
ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library
ii libncurses5 5.5-3 Shared libraries for terminal hand
ii libpango1.0-0 1.14.4-2 Layout and rendering of internatio
ii libruby1.8 1.8.5-2 Libraries necessary to run Ruby 1.
ii libsm6 1:1.0.1-3 X11 Session Management library
ii libx11-6 6.8.2.dfsg.1-9 X Window System protocol client li
ii libxcursor1 1.1.3-1 X cursor management library
ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte
ii libxfixes3 6.9.0.dfsg.1-4 X Window System miscellaneous 'fix
ii libxi6 6.9.0.dfsg.1-4 X Window System Input extension li
ii libxinerama1 6.8.2.dfsg.1-9 X Window System multi-head display
ii libxrandr2 6.9.0.dfsg.1-5 X Window System Resize, Rotate and
ii libxrender1 1:0.9.0.2-1 X Rendering Extension client libra
ii libxt6 6.8.2.dfsg.1-11 X Toolkit Intrinsics
ii vim-common 1:7.0-094+1 Vi IMproved - Common files
ii vim-gui-common 1:7.0-094+1 Vi IMproved - Common GUI files
ii vim-runtime 1:7.0-094+1 Vi IMproved - Runtime files
vim-ruby recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Sep 29, 2006 at 04:27:31PM +0200, Maurizio Lemmo (Tannoiser) wrote:
> * venerdì 29 settembre 2006, alle 10:15, James Vega scrive:
> > > I always test this with "vim -u NONE" start command. I tested different
> > > flavor of LANG variables (C, en_US...), but no luck.
> >
> > Invoking vim as "vim -u NONE" will always cause this behavior since Vim
> > is in vi-compatible mode. If you still see the problem when invoking
> > VIm as "vim -u NONE -N", then there is a problem. I was unable to
> > reproduce this using "vim -u NONE -N" with vim-ruby.
>
> Thank you James, for your promptly response.
>
> You have a point. With "vim -u NONE -N" there's no problem at all. So,
> this bug is bogus, and I apologize.
>
> Probably something in my .vimrc do this to me, even I had the "set
> nocompatible" in it.
Be sure 'set nocompatible' is the first thing that is set in your
.vimrc. It changes many other options (as noted in :he 'compatible')
when it is set.
Good luck tracking down the rogue setting. :)
James
--
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
--- End Message ---
