Rod.. Whitworth wrote: > > I have used lynx for years as a file browser as well as web browser > (when I can) and it is routine for me to "fix" /etc/lynx.conf to show > me dotfiles. > > Recently I need to inspect lots of text files and sometimes edit a few > so I set vi to be the system editor for lynx. So far so good. > > When editing small files I noticed that vi complained that there were > only x lines (for some value of x greater than wc -l for the file) and > on larger files the cursor was always some distance from the first > line. > > Finally it bugged me enough that I used "ps www|grep vi " to see that > vi was being started with -c9 (as an example) and from there it grew. > Tonight I found that it went from 9 to 16, 29, 31, 40, 49, 50, 56. It > is not always the same sequence. Just now it began at 8. > > I grepped around for anything like "vi -c" to no avail. I though that > was too obvious anyway. > > Somebody is probably smiling quietly right now and feeling > appropriately superior. > > If that is you please demonstrate your advanced clues and put me out of > my misery. > > WTH is going on? I don't get it. > > Thanx, > Rod/ > > > >From the land "down under": Australia. > Do we look <umop apisdn> from up over? > > Do NOT CC me - I am subscribed to the list. > Replies to the sender address will fail except from the list-server.
Wild guess, but seems like vim (vi?) likes to store various info about when you last edited a file in some kind of dotfile. Wild guess is that somehow the dotfile itself is being parsed by vi as this file with assorted info in it. It might also be trying to start at the same location in the "next" file as you left it in the "previous" file. I have an alias vim='vim -N' (3.8 vintage) to avoid something strange (forget exactly what) You maybe will get better answers from somebody who actually knows something ;) You may have lynx now deciding to be "user friendly" (Nice thoughts, but often backfires;)
