fREW wrote:
> On 5/22/07, fREW <[EMAIL PROTECTED]> wrote:
>> On 5/22/07, Gene Kwiecinski <[EMAIL PROTECTED]> wrote:
>> > >I just updated to feisty on a samba server machine and a lot of the
>> > >vim defaults went crazy. For example: Pressing the Up or Down keys
>> > >in insert mode add new lines with just A or B on them, respectively.
>> >
>> > Sounds like it stopped recognising arrow keys' ANSI sequences
>> ("<esc>[A"
>> > and "<esc>[B"). Wouldda thought the <esc> would break out of insert
>> > mode, but...
>> >
>> >
>> > >That I can live with, but check this out, if I have the following
>> > >sentence:
>> > >fREW is a silly guy
>> > >and my cursor is on the s, and I press cw, it changes to
>> > >fREW is a sill$ guy
>> > >and it works just like I had pressed cw and it replaces up the the $
>> > >or if I press escape it only has the new text I put in, but it's just
>> > >so weird! Does anyone know where these new changes in Feisty come
>> >
>> > Uhh, sounds like what it's supposta do, no? ??
>> >
>> > Is there a problem with actually changing the text, or just what's
>> > displayed? Dunno the setting offhand, but a slow-redraw will mark to
>> > the end of the text to be replaced, eg, if you were to change to the
>> end
>> > of the line, you'd still see the whole line, but with a '$' where the
>> > last character would be, vs erasing all the text and just leaving the
>> > insert-cursor in its place. I find the latter disquieting, and would
>> > rather *see* what I'm replacing, but never really paid too much
>> > attention to which settings do what. I'm complacent that way... :D
>> >
>>
>> I prefer that cw doesn't do this weird $ thing. It bothers me. I
>> might be ok with it if the word I was typing over were a different
>> color, but that is not the case.
>>
>> Also: set nocompatible worked just fine, but I wanted to make this a
>> system wide setting. I think that the problem has to do with vim not
>> sourcing the /etc/vim/vimrc. It appears that that is why things
>> aren't working correctly. Anyone know why it wouldn't source that
>> file?
>>
>> -fREW
>>
>
> I figured it out and if anyone else has this problem I am sending out
> the solution. Basically when I run vi it is running vim.tiny.
> vim.tiny sources /etc/vim/vimrc.tiny, not /etc/vim/vimrc, also,
> vim.tiny is pretty crippled, in that it doesn't even have syntax
> highlighting, so consider whether that's even what you want.
This is by design. Note that vimrc.tiny is /only/ sourced when vim.tiny
is invoked as vi. This is a Debian/Ubuntu extension; unmodified vim has
no notion of vimrc.tiny.
As at least one person has noted, there are many users who expect a
vi-compatible program when they type "vi" at the command-line. When this
isn't what you want, you really should consider changing your habit to
use vim, as that way you are sure to get a featureful vim, if one is
installed ("vi" could get you any one of a number of programs, depending
on the system you're on).
To switch your "vi" to pull a real vim, you might consider installing a
vim such as vim-gnome or vim-full (these are Debian names), and using
update-alternatives to set vi to be one of those instead of vim-tiny.
Actually, current default is for vi to point at /usr/bin/vim, so if your
update-alternatives has vim set to /usr/bin/vim.gnome or
/usr/bin/vim.full, your vi will probably start sourcing vimrc instead of
vimrc.tiny. This may change in the future (vi may default to
/usr/bin/vim.tiny instead of /usr/bin/vim).
Further discussion of this should possibly be moved to the Ubuntu or
Debian forums (I'm not certain how much of this may be specific to
Ubuntu as opposed to Debian; the source code changes included macro
names with "DEBIAN", in them, so I'm assuming that most of the
decision-making for this was made by Debian developers).
--
HTH,
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/
signature.asc
Description: OpenPGP digital signature
