On Mon, Dec 7, 2015 at 10:53 AM, Viacheslav Lotsmanov
<[email protected]> wrote:
> @chrisbra actually I tried this config at first:
> https://github.com/unclechu/vimrc2/blob/master/.vimrc where I have
> nocompatible flag and I have this bug in this mode too.
>
> In v7.4.827 (from Fedora 22 repos) I have no this bug.
>
> It looks like main reason of this it's that I have empty bs option. I built
> v7.4.827 from git and I don't have anything in bs option, but I always have
> something in bs from vim-builds from many distros, only if I build it from
> sources it's empty.
>
> Anyway it definitely looked like bug for me, and I couldn't understand that
> I need to ask about it in mailinglist.
>
"Tain't a bug, it's a feature". In this case a feature which
ultimately goes back to Bram's (IMHO commendable) attention to
backward compatibility, since the default is vi-compatible.
I recommend sourcing the vimrc_example.vim at startup, for instance by having
runtime vimrc_example.vim
somewhere near (but not necessarily exactly at) the top of one's
vimrc. This takes care of setting many "more fashionable" settings
than what used to be in fashion in vi's heyday, and in particular it
sets 'backspace' to "indent,eol,start" which suits me perfectly. My
guess is that the same 'backspace' setting would suit you too.
Best regards,
Tony.
--
«I have a problem with my editor.
— Which editor is it?
— The one which came with the computer.
— Well, which version?
— Version six (VI).
— You should upgrade to version six thousand (VIM).»
--
--
You received this message from the "vim_dev" 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_dev" 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.
