Hi! On Sun, May 04, 2008 at 11:42:53AM -0400, Nick Holland wrote: >ropers wrote: >> 2008/5/4 Nick Holland <[EMAIL PROTECTED]>: >>> "[vim] alters files in unexpected ways", which I consider a >>> major sin.
>> I didn't know that, and cursory googling didn't turn up anything >> enlightening. Could you elaborate? >> Thanks and regards, >> --ropers >It might have been better if I had said, "alters my input", instead >of implying that I edit a file with vim and it gets saved >differently than loaded without my deliberately changing anything. >And yes, tabs and auto indent were some of the things. Now, nvi has auto-indent too (:set ai), just not enabled by default. >I also had >an experience with it auto-inserting line breaks which caused me >large amounts of problem. Could happen with nvi too (:set wrapmargin=42). Just not enabled by default. >All this stuff is there for a reason, and is great for the >intended purposes. HOWEVER, it's annoying as heck when one's >purposes don't jive with the editor's defaults. Now, on *OpenBSD*, the defaults of vim are quite sane IMO. (I.e. syntax highlighting, auto-indent, text wrapping, smart-tabs, tab expansion, etc. *off* by default, I have to enable all the fancy I really want in my $HOME/.vimrc). It's vim as it's distributed on some Linux distributions that sucks rocks through tiny holes. >Yes, all those >defaults can be changed, but on the machine I was fighting with >at the time, they were in some very inappropriate for my needs, and >quite unexpected behavior for something I invoked with the command >"vi". I won't dispute vim is a great editor...I just dislike it >pretending to be vi on some distributions of another OS. In all >likelihood, it COULD pass as vi, but not with all the options >turned on. Yes. Probably it works for me especially because I mostly use it on OpenBSD. :-) >Nick. Kind regards, Hannah.
