Gary Johnson wrote:
> On 2011-09-07, Gary Johnson wrote:
> > On 2011-09-07, James Vega wrote:
> > > On Wed, Sep 07, 2011 at 02:16:59PM -0700, Gary Johnson wrote:
> > > > When a buffer is modified by a BufRead autocommand or by a filetype
> > > > plugin, 'modified' is not set.
> > >
> > > This is
On 2011-09-07, Gary Johnson wrote:
> On 2011-09-07, James Vega wrote:
> > On Wed, Sep 07, 2011 at 02:16:59PM -0700, Gary Johnson wrote:
> > > When a buffer is modified by a BufRead autocommand or by a filetype
> > > plugin, 'modified' is not set.
> >
> > This is documented in the text below ":help
On 2011-09-07, James Vega wrote:
> On Wed, Sep 07, 2011 at 02:16:59PM -0700, Gary Johnson wrote:
> > When a buffer is modified by a BufRead autocommand or by a filetype
> > plugin, 'modified' is not set.
>
> This is documented in the text below ":help gzip-example".
>
> The commands executed fo
On Wed, Sep 07, 2011 at 02:16:59PM -0700, Gary Johnson wrote:
> When a buffer is modified by a BufRead autocommand or by a filetype
> plugin, 'modified' is not set.
This is documented in the text below ":help gzip-example".
The commands executed for the BufNewFile, BufRead/BufReadPost,
BufWri
When a buffer is modified by a BufRead autocommand or by a filetype
plugin, 'modified' is not set.
To show this, create a simple file (testfile) containing these
lines:
abc
def
ghi
>From a shell prompt, execute this command:
vim -u NONE --cmd 'au BufRead * %s/e//' -c 'set lastst
