Your message dated Sun, 21 May 2006 09:02:53 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368276: vim configuration not found anymore?
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
Version: 1:7.0-017+3
The configuration is now in /etc/vimrc and /usr/share/vim/vim70/debian.vim
But changing something in any of these files does not have any effect.
Putting something into ~/.vimrc is recognized, but it starts from something
so minimal, that the program cannot be used productively anymore.
$ vim bla.c
:set
--- Options ---
ttyfast ttymouse=xterm
That's it.
Many features that worked earlier thus seem deactivated, making vim virtually
unusable.
Among them:
- Backspace does not delete properly anymore in insert mode, instead spaces
are written over the text which disappear first after leaving insert mode,
leaving
the rest of the line after the cursor unmoved while deleting.
- Keeping : history. History is zero per config. It is empty when calling vim
even
there were commands before.
I completely removed vim and the old configs and installed it newly without
effect.
--- End Message ---
--- Begin Message ---
On Sun, May 21, 2006 at 12:33:36PM +0200, [EMAIL PROTECTED] wrote:
> So why is this setup not longer respected?
That setup is still respected. Just because vi is a symlink to vim
doesn't change how you are invoking the program.
> The link chain as odd as it looks first does
> well allow to clarify the situation. Why adding another twist that is
> inferior and only breaks this chain?
The change occurred because of a discussion on debian-devel regarding
having vim replace nvi as the vi-like editor in base. Part of the
decision was that vim should act as much like vi as possible when
invoked as vi.
I find this to be a completely reasonable behavior. A user should
expect vi to invoke vi (or something very similar) and doing anything
else is just helping to develop bad muscle memory.
> Of course i can add a "vi=vim"
> alias now - as suggested in the NEWS - but given that setup what does
> the new vi -> vi enforcement help?
There are many systems where vi is different or behaves differently than
vim, so I think it is a good thing to enforce the mental model of them
being different. You have the option of setting up a shell alias (or
adding 'set nocompatible' to your ~/.vimrc) if you want vi to work as
vim instead of vi.
James
--
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
--- End Message ---
