On 12/02/11 12:26 AM, Pedro Gomes wrote:
Hi,
Yes, I tryed this in my Ubuntu machine and had no such problem. I found a
workaround if I have the following lines in the beggining of my _vimrc, it will
reset all options and I will see no problem.
/" Clean everything beforehand so we can start as fresh as possible
" 1) Reset all options to default
set all&
Excellent!
That means we can narrow down the problem by looking at your settings.
Can you do this, please:
:redir @"
:set
:redir END
:new
:put
and send the results? That will show us all the settings you have that
are different to defaults and we can possibly find out which is causing
the problem. (Or even better, if you're able to isolate which is causing
the problem, perhaps by moving the set *prg lines lower in your .vimrc
until they start causing problems at startup, that'd save some time for
another developer!)
Concerning your question, yes it also shows the problem. I believe
there is some option that I'm setting in the _vimrc that is breaking
the interpretation of the *prg options when escaped sequences appear.
It's strange that the option that get set in the case of error is only
parsed until the escaped space character.
Yeah, I think this is probably a problem with how the set command works,
not the *prg options in particular. You can have multiple options in a
set command separated by spaces, and for some reason the backslash is
being ineffective to escape it, but only when some other option is set
(strange).
Ben.
Maybe Bram can be of some help. There maybe some option precondition that I'm at
least am not aware of (related to enconding perhaps).
Regards,
Pedro
On Fri, Feb 11, 2011 at 9:40 AM, Ben Schmidt <[email protected]
<mailto:[email protected]>> wrote:
On 10/02/11 4:50 AM, Azynheira wrote:
Hello All,
If I have the following statements in my _vimrc:
set makeprg=nmake\ -n
set formatprg=par\ -w78j
set grepprg=grep\ -nH
(G)vim loads properly, but if I have the following to make _vimrc
reload on changes:
autocmd BufWritePost _vimrc source d:\vim\_vimrc
And I provoke an update of the _vimrc file via ':w" for example, all
the above stated set lines fail with the following errors
respectively:
Unknown option: ' -n'
Unknown option: ' -w78j'
Unknown option: ' -nH'
What seems to be the problem ?
This is strange. I suspect it's Windows-related, but I'm guessing.
What happens if you issue
:source d:\vim\_vimrc
on the commandline rather than in the autocommand? Do you get errors in
that case?
Ben.
--
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 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 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
