Hans Günter wrote:
> I found an inconsistency between the makeprg option in compiler files and
> the isfname option when the latter has a space (32) as element.
>
> To reproduce the problem perform the following steps:
>
> 1) start vim via:
> vim -u NONE -U NONE --noplugin
> 2) Add space to the isfname option:
> :set isf+=32
> 3) Start a compiler whose makeprg option has embedded spaces e.g. to
> add command line parameters:
> :compiler fortran_cv
>
> You then will see a message like:
>
> Error detected while processing c:\Program Files\vim\vim72\compiler
> \fortran_cv.vim:
> line 25:
> E518: Unknown option: /nologo\ /noobj\ /c\ %
> Press ENTER or type command to continue
>
> The Unknown option part ist the rest of the makeprg option value in
> fortran_cv.vim following the first space there.
>
> I saw this problem in vim 7.2 and vim 7.2.267.
Don't add a space to 'isfname'. Quote from the help:
Think twice before adding white space to this option. Although a
space may appear inside a file name, the effect will be that Vim
doesn't know where a file name starts or ends when doing completion.
It most likely works better without a space in 'isfname'.
--
A special law prohibits unmarried women from parachuting on Sunday or she
shall risk arrest, fine, and/or jailing.
[real standing law in Florida, United States of America]
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
