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
--
Never hold a dustbuster and a cat at the same time.
Christian J. Robinson <[EMAIL PROTECTED]> http://infynity.spodzone.com/
PGP keys: 0x893B0EAF / 0xFB698360 http://infynity.spodzone.com/pgp
