I don't observer Raffi's behavior with vim. Of course the vi we now get by
default doesn't work as it used to. My solution:
edit .bashrc and
alias vi=vim
cest la vie...
wcn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm experiencing a variation on this bug, and the unfortunate downside
is that I'm prevented from using one of my favorite Vim features. I can
use the arrow keys in insert mode just fine, but when I type forward
slash / to search the file, and hit the up arrow key (to browse my
search history),
Well there's some dispute over whether it's actually a bug. But for
someone unfamiliar with vi/vim how one or the other's 'supposed' to
work - perhaps using it to edit some config files because they can't
boot into the GUI - the current situation could render this tool
unusable. For them, it
this cheap bug still in 8.10
--
Arrow keys are incorrectly mapped in vim
https://bugs.launchpad.net/bugs/62980
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This behaviour does seem a bit odd. It has kept me guessing for about a
day. What's one of the first things I want to do after installing
Ubuntu? Edit some text files...
If you want to keep the distro space down, maybe vi can be set by
default as an alias of some sort to vim?
--
Arrow keys are
The 'vim' command is already there by default (vim-tiny is installed).
If you want vim, use the 'vim' command. Vi isn't vim.
In response to Reuben, there is nothing to revert. The 'vi' command has
always been this way.
In response to Liegerm, isn't the 'vim' command already there after
Sorry for the spam, but I should point all of you to bug 70569 as well,
which pertains to the issue, and explains why there is some confusion
over what vi does.
--
Arrow keys are incorrectly mapped in vim
https://launchpad.net/bugs/62980
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I also agree that vi should work as it did. I've been using ubuntu
since hoary, and to my recollection the arrow keys have always worked as
I have expected (and, I've used a large number of distributions since
'99, and don't remember any of them shipping by default w/out intuitive
arrow key
Thank you for your report, but this is actually the intended behaviour
of the vi command. When invoking vim-tiny, the variant of vim installed
by default, using the vi command, it reads /etc/vim/vimrc.tiny, which
sets the compatible mode, so that vi acts like the original vi. The
broken arrow keys
This is really funny explanation, I am sure that majority off users
expect that vi command actually point's to vim, as it was case with
prior ubuntu versions. Probably there should be option via dpkg-
reconfigure to use vi compatibility
--
Arrow keys are incorrectly mapped in vim
The intended behaviour is to have vi use set compatible, as noted in the
vim manpage, /etc/vim/vimrc.tiny, and a variety of other places. The
behaviour in Dapper was a bug. In fact, I've even filed a bug report
about this (bug 70569).
--
Arrow keys are incorrectly mapped in vim
any why
there will be always more people who expect vi to behave like vim then other
way that is obviously joust look at this bug how many duplicates it have
already. :)
And if user expect that arrow keys behave like vi then this is mostly power
user who now how to fix this :)
** Changed in:
I totally agree that the default behavior should be for it to be mapped
like vim. Ubuntu's slogan of having things Just work should apply
here. The majority of users will consider this to be broken until the
mappings are restored to the way it was previously configured in dapper.
--
Arrow keys
Why, in compatibility mode the arrows, are not interpreted?
--
Arrow keys are incorrectly mapped in vim
https://launchpad.net/bugs/62980
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Nicolò, the arrow keys aren't mapped because compatibility mode acts
exactly like the original vi, down to bugs if I recall correctly.
For this bug, I can understand the desire to have vi start vim. However,
if someone wants to start vim, they need to run vim. One wouldn't use
the command emacs
I can confirm this too: when /usr/bin/vim.tiny is run normally (with an
argv[0] of .../vim.tiny) the arrow keys work as expected, and as they
did on Dapper. When the same binary is run as vi instead, it gets the
arrow keys wrong. This looks like a vim (or vim configuration) bug.
--
Arrow keys
Same thing was here when using vi as sudo arrow keys where wrongly mapped
if used vim it was OK, also after installing vim.full it is all working OK
--
Arrow keys are incorrectly mapped in vim
https://launchpad.net/bugs/62980
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I get similarly unusable key mappings as this using a very generic
desktop, uk keyboard, and the edgy rc with all updates as of writing
applied.
I get exactly the same as the duplicate bug 67105 whilst in a gnome-
terminal and very different but equally unusable key mappings whilst in
a regular
** Changed in: vim (Ubuntu)
Status: Unconfirmed = Confirmed
--
Arrow keys are incorrectly mapped in vim
https://launchpad.net/bugs/62980
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
19 matches
Mail list logo
