On 16 October 2015, LCD 47 <[email protected]> wrote:
> On 16 October 2015, Christian Brabandt <[email protected]> wrote:
> > Hi Nicola!
> >
> > On Do, 15 Okt 2015, Nicola wrote:
> >
> > > On 2015-10-15 14:54:17 +0000, Gary Johnson said:
> > >
> > > >To solve the particular problem of setting 'errorformat' without
> > > >disturbing the global setting, you could either set the value for
> > > >just the current buffer like this:
> > > >
> > > > setlocal errorformat=%f:%l:%m
> > >
> > > I have tried that, but cexpr (and lexpr, too!) uses the global value
> > > of errorformat.
> >
> > Sounds like a bug to me. Does this patch fix it?
> [...]
>
> Are you sure this is a bug? There is no reason for the result of
> cexpr / lexpr to depend on the current buffer. The change you suggest
> would be backwards incompatible, for no real gain as far as I can tell.
The current behaviour is even documented:
: If {expr} is a String, then each new-line terminated
: line in the String is processed using the global value
: of 'errorformat' and the result is added to the
: quickfix list.
/lcd
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
