Yeh, ..modeline. The name escaped me at that moment, so I just blasted the string, sorry :-)
For something that stores information univerally, I think a couple autocommands (at shutdown to store the item, and startup to restore) would do the job; essentially, you'd be creating a companion .viminfo file which would hold just the info you're interested in. If you're storing information, and tagging it with the filename, restoring on startup should be a snap, i.e. it wouldn't have to do any intelligent evaluation. >From what I think you were saying, you're not so interested in automatically setting new values for new files, but saving existing values from files you've already visited. I'm assuming you'll have no problem implementing such a thing, but I could look for some examples... --- Yakov Lerner <[EMAIL PROTECTED]> wrote: > On 4/9/06, Eric Arnold <[EMAIL PROTECTED]> wrote: > > --- Yakov Lerner <[EMAIL PROTECTED]> wrote: > > > > > Some of the files I use are 8-tabbed, some are 4-tabbed. > > > These files are readonly, so modelines are not an option. > > > (I am talking about \t tabs, not about vim7 tabpages). > > > > > > Viminfo remembers last position in the file. When I > > > reopen file, vim remembers last position. > > > > > > Is there any way to tell vim to remember the last tabstop-related > > > options per file in the viminfo ? > > If you use the > > > > " vim6:fdm=marker:foldenable:ts=4:sw=4 > > This thing is called "modeline". I can't modify those files so I > can't use modelines for then (when I can use modelines, I use them). > For some files I cannot use modelines. Then I manually set > tab-related options (via shortcut mappings). I just thought > why would vim not remember tabbing-related options in the > viminfo ? > > Yakov > mappings >
