On Wed, 31 May 2006 at 11:47pm, Christian J. Robinson wrote: > Today (Wed, 31 May 2006), Hari Krishna Dara wrote: > > > The handling of FileChangedRO was never smooth for me. As a > > workaround, I am thinking of avoiding a reload altogether and just > > mark the buffer as 'noro'. I relied upon the reload for its side > > effects before, but I should be able to force them directly, so all > > I can think of that needs to be done after a successful checkout is > > to mark the buffer as non-readonly. Any comments? > > My problem with that is that RCS's "co"/"ci" commands modify the file > on disk if you have some of the special $...$ tags within the file, so > a reload of the buffer is essentially mandatory. > > - Christian
Thanks for pointing this out... even perforce supports some keywords, so reloading is essential for me as well. -- Thanks, Hari __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
