On 26 October 2015, Ben Fritz <[email protected]> wrote:
> On Monday, October 26, 2015 at 5:11:38 AM UTC-5, LCD 47 wrote:
> > Summary: parsing %f with errorformat depends on isfname. It
> > probably shouldn't.
> >
>
> Why? 'isfname' tells Vim what characters are considered file name
> characters. Why on earth shouldn't Vim pay attention to "what is a
> file name character?" when it is parsing an errorformat item that is
> "a sequence of file name characters"?
Because the default value for 'isfname' is not the set of characters
valid in a filename on the current system, but a subset of said
set carefully crafter so that it works for things like <cword> and
completion. As I shown in my previous message, on UNIX that doesn't
include space and apostrophe. Sadly, people using plugins such as
syntastic would like to check files with such names once in a while.
> I'd consider it a bug if Vim DIDN'T pay attention to 'isfname' when
> parsing %f items.
Did you read my initial message? %f only pays attention to 'isfname'
if the character following %f is \ or %. Thus the difference in handling
%f: and %f\, . Good news for syntastic, half of the 188 checkers will
work as expected. The other half will depend on 'isfname', and the
solution to set the 'isfname' to fix them will also depend on the OS.
Hardcore Vim, I tell ya.
/lcd
--
--
You received this message from the "vim_dev" 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_dev" 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.
