On 2007-09-23, "Ed S. Peschko" <[EMAIL PROTECTED]> wrote:
> ok, I see your points about why matching isn't on by default... but surely
> couldn't
> this all by encapsulated by:
>
> :mtc on
>
> the same way that
>
> :syn on
>
> toggles on syntax highlighting?
What do you e
Here's what MicroSoft is up to for console/terminal:
http://www.powershell.com/plus/
Weird that that thing seems to still have only 16 colors!
It is possible to try out PowerShell (a shell, not a
console/terminal) today. Commands in PowerShell do not
move text data via pipes;
ok, I see your points about why matching isn't on by default... but surely
couldn't
this all by encapsulated by:
:mtc on
the same way that
:syn on
toggles on syntax highlighting?
Ed
> >> a given file, yet 'matchit' turned off?
> >>
> >> IMO, This makes no sense -
Ed S. Peschko wrote:
> ps -
>
> where exactly are the b:match_words variables defined for a given language?
>
> I would have thought it would be as easy as saying:
>
> :source $VIMRUNTIME/macros/matchit.vim
>
> to get the correct b:match_words variable for my current extension being
>
Hi, guys.
I've posted on vim_use some days before:
>$ vim -c "q" 'foo ~ foo'
>$ vim -c "normal '0"
>E20: Mark not set
Filename contains '~' character which is around with path separators
(i.e. ' ' and ',') has such problem.
And the patch:
Index: mark.c
ps -
where exactly are the b:match_words variables defined for a given language?
I would have thought it would be as easy as saying:
:source $VIMRUNTIME/macros/matchit.vim
to get the correct b:match_words variable for my current extension being edited,
but this doesn't work.
Is ther
All,
I've been editing html files as of late, and have run into some usability snags.
In particular - what's the rationale behind having syntax coloring turned on
for
a given file, yet 'matchit' turned off?
IMO, This makes no sense - you need to bounce between tags to get anything
done with
