There seems to be a bug in the built-in CompilerSet command used to
set compiler-related options in compiler plugins: it doesn't record
where its argument options are set for later use by a ":verbose set
<option>?" command.
For example, the compiler/gcc.vim plugin sets 'cpo' and uses
CompilerSet to set 'errorformat'. If I execute the following,
$ vim -u NORC foo.c
:compiler gcc
:verbose set cpo? efm?
cpoptions=aAbBcCdDeEfFgHiIjJkKlLmMnoOpPqrRsStuvwWxXyZ$!%*-+<>
Last set from /usr/share/vim/vim72/compiler/gcc.vim
errorformat=%*[^"]"%f"%*\D%l: %m,"%f"%*\D%l: %m,%-G%f:%l: %trror: (Each
undeclared identifier is reported only once,%-G%f:%l: %trror: for each function
it appears in.),%f:%l: %m,"%f"\, line %l%*\D%c%*[^ ]
%m,%D%*\a[%*\d]: Entering directory `%f',%X%*\a[%*\d]: Leaving directory
`%f',%D%*\a: Entering directory `%f',%X%*\a: Leaving directory `%f',%DMaking
%*\a in %f
I see where 'cpo' was set, but 'efm' appears not to have been set
since startup.
This is a problem when trying to troubleshoot problems with
configuring compiler settings.
That particular experiment was run on Vim 7.2.148 on Linux, but I
see the same behavior from 7.3.46 on Windows.
Regards,
Gary
--
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
