[ale] inode change after vi a file ?

[Chris Ricker]

On Thu, 30 Mar 2006, Jerry Yu wrote:

> so it's something in the code of vi or kernel code (ext? fs code)?   It
> doesn't sound like the sane behavior to a layman. starts to smell like a
> tiny bug ...
> tried a few other editors.  oowriter (open office word) and 'nano' do not
> change inode #.  gedit changes it for every save.

it's vim, and it's a feature. Doing all the changes in a temp file then 
renaming it gives you more change for recovery to a sane state if 
something goes wrong....

AT & T vi doesn't do that, BTW. Don't know about the other vi 
implementations (nvi, for example)

later,
chris