On Sun, 18 Jun 2006 at 11:26pm, Bram Moolenaar wrote:
Hari Krishna Dara wrote:
It seems like I am getting E788 error too often, without much reason.
The latest is for the :compiler command that is being executed from a
ftplugin. I narrowed it down to the command itself, not the compiler
Hari Krishna Dara wrote:
The previous time I got E788 was in my FileChangedShell handler. Prior
to 7.0, since there was no v:fcs_reason support, I had to jump to the
buffer for which the event got triggered and conditionally reload the
buffer, but now this is no longer allowed. The
On Mon, 19 Jun 2006 at 9:48pm, Bram Moolenaar wrote:
Hari Krishna Dara wrote:
The previous time I got E788 was in my FileChangedShell handler. Prior
to 7.0, since there was no v:fcs_reason support, I had to jump to the
buffer for which the event got triggered and conditionally
Hari Krishna Dara wrote:
It seems like I am getting E788 error too often, without much reason.
The latest is for the :compiler command that is being executed from a
ftplugin. I narrowed it down to the command itself, not the compiler
plugin, as adding a :finish at the start of the compiler
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
It seems like I am getting E788 error too often, without much reason.
The latest is for the :compiler command that is being executed from a
ftplugin. I narrowed it down to the command itself, not the compiler
plugin, as adding a :finish at the start of the compiler plugin didn't
get rid off the
Today (Wed, 31 May 2006), Hari Krishna Dara wrote:
It seems like I am getting E788 error too often, without much
reason. The latest is for the :compiler command that is being
executed from a ftplugin.
[...]
I get this error as well. There really needs to be some kind of
compromise--I'm only
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
