On 10/23/07, Andy Wokula <[EMAIL PROTECTED]> wrote:
> Richard Hartmann schrieb:
> > On 23/10/2007, Andy Wokula <[EMAIL PROTECTED]> wrote:
> >> :syn region zshSubst matchgroup=zshSubstDelim start='\${' skip='\\}'
> >> \ end='}' [EMAIL PROTECTED],zshBrackets,zshQuoted,zshString
> > This
Aryeh Leib Taurog wrote:
> Occasionally, when I run vim, it clears the terminal, prints an error
> message and exits immediately.
>
> This has happened very infrequently and I actually thought it was a
> problem with my terminal (terminator Revision 1346 (2308)), but now it
> is happening (wit
On 23/10/2007, Andy Wokula <[EMAIL PROTECTED]> wrote:
> I have a menu map to this insightful command:
> :exe "hi" synIDattr(synID(line("."),col("."),1),"name")
Stolen for my vimrc, thanks :)
I will contact Nikolai off-list and report back here.
Richard
--~--~-~--~~---
Occasionally, when I run vim, it clears the terminal, prints an error
message and exits immediately.
This has happened very infrequently and I actually thought it was a
problem with my terminal (terminator Revision 1346 (2308)), but now it
is happening (with more consistency, unfortunately) un
Richard Hartmann schrieb:
> On 23/10/2007, Andy Wokula <[EMAIL PROTECTED]> wrote:
>
>> :syn region zshSubst matchgroup=zshSubstDelim start='\${' skip='\\}'
>> \ end='}' [EMAIL PROTECTED],zshBrackets,zshQuoted,zshString
>
> This fixes the bug. Is there any defined path to get this into t
On 23/10/2007, Andy Wokula <[EMAIL PROTECTED]> wrote:
> :syn region zshSubst matchgroup=zshSubstDelim start='\${' skip='\\}'
> \ end='}' [EMAIL PROTECTED],zshBrackets,zshQuoted,zshString
This fixes the bug. Is there any defined path to get this into the
standard distribution or do we ju
Richard Hartmann schrieb:
> Hi all,
>
> Problem:
> vim zsh syntax file gets confused by curly brackets in single quotes.
>
>
> Test cases:
> A=${foo['A']}
> B=${foo['{']}
> C=${foo['C']}
>
> A=${foo['A']}
> B=${foo['}']}
> C=${foo['C']}
>
> Lines 1 and 3 are irrelevant to the outcome, they ju
Hi all,
Problem:
vim zsh syntax file gets confused by curly brackets in single quotes.
Test cases:
A=${foo['A']}
B=${foo['{']}
C=${foo['C']}
A=${foo['A']}
B=${foo['}']}
C=${foo['C']}
Lines 1 and 3 are irrelevant to the outcome, they just provide examples
of correct and broken syntax hilightin
> You might have better luck running some "pseudo-X11 server"
> like vnc server which can run on Linux/Unix machine
> without any graphics hardware (but *not* x11vnc).
I think Xvfb is the easiest way:
http://en.wikipedia.org/wiki/Xvfb
It's truly virtual and is a part of X.org project.
But it i
>> Somehow using a dollar doesn't work here, probably because of expanding
>> environment vars. We might not be able to change this without breaking
>> backwards compatiblity.
>
> This is completion-specific issue. In glob, the problem does not exist.
>
> Strangely, :e $ completes names of env.
On 10/22/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
>
> Yakov Lerner wrote:
>
> > Would you add to the todo list some way to lock the
> > filename completion to the end of the filename ? Currently, the
> > :e *a
> > automatically adds the * at the end. This shows not
> > files endnig with
11 matches
Mail list logo