sc wrote: > i tried upgrading to v135g, and i changed formatoptions to > 'tco' in my .vimrc to mirror your attempt > > i used my 'vime' to start the session, selected a file, and > fo was 'tco' -- fine -- i used MyExplore to find and add > another buffer, fo was again 'tco' -- fine -- i used > MyExplore to add two more buffers in the same way, tco was > still the fo for each of the added buffers -- fine -- then i > quit a buffer with my bdelete key and presto the > formatoptions were 'nroql2' in the buffer i quit back to, > which had previously reported 'tco', the only difference > being now the verbose set? reports it was last set from > ~/.vim/autoload/netrw.vim (which is where i dropped v135g) > > i've also reproduced this in gvim, so it appears not to be > confined to vim > > if there is more information i can give you to help you > reproduce this, please tell me -- i'd really like to see it > fixed so i can start trusting netrw again >
I'd appreciate it if you would give me an exact sequence of instructions to cause the problem, preferably in a script form. Thank you! Chip Campbell --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
