> On 2011-11-26, Ben Fritz wrote:
>
> > On Nov 26, 6:48 pm, Marvin Renich wrote:
>
> > > Don't confuse :make with :!make. While internally, :make is going to
> > > execute the OS's make command (assuming default 'makeprg'), the behavior
> > > of | in this context depends on the result of the vim command :make, not
> > > the result of the OS make.
>
> > The '|' in the context of Vim ex commands never depends on the result
> > of any previous command, except for control-flow commands
> > like :if, :else, etc.
>
> From ":help :bar":
>
> Note that when the command before the '|' generates an error,
> the following commands will not be executed.
>
I meant, the '|' doesn't depend on the result of Vim commands which
run to completion without throwing an error. I suppose now that I re-
read this thread, that one could expect that :make could throw such an
error.
But this thought never occurred to me, because the whole point
of :make is to gather errors from an external process and make them
available in Vim. I expect Vim commands to throw errors only if
something went wrong. If :make successfully gathers all errors, I
would expect no error in Vim.
But now I can see how this might be unexpected.
--
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
No comments:
Post a Comment