Re: non-greedy matching?

Re: non-greedy matching?

[Sven Wischnowsky]

Adam Spiers wrote:

> ...
> 
> Any ideas? 

No (I'm still worried about what I wrote in the other mail to
-workers), but:

> The only alternatives I've come up with are:
> 
>   foo=$(print -P "$prompt_string")

No need for that extra sub-shell there, use ${(%):-$prompt_string} or
${(%%):-...} depending on what you want...


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de

non-greedy matching?

[Adam Spiers]

Sorry, I seem to be coming out with a lot of dumb questions recently.

In my quest to improve my zsh startup time, I noticed to my horror
that when I initially coded prompt_adam2_setup, I made it invoke perl
no less than three times.  Eliminating one of them is fairly easy;
however the other two invocations are:

  ..... | perl -pe 's/%{.*?%}//g'

They are done in order to strip control characters from a prompt so
that its display width can be determined.  At first I thought that it
would surely be easy to avoid this, but I still haven't come up with a
quick replacement, since neither zsh nor sed seem to be able to do
non-greedy matching.

Any ideas?  The only alternatives I've come up with are:

  foo=$(print -P "$prompt_string")
  bar="${foo//^[[[0-9;]##m/}"

the string and then strip out ANSI escape sequences, or maybe to use
the (^(...)) extended glob somehow, but I haven't managed to get the
latter working.

It would be nice if zsh could do non-greedy though.

Re: non-greedy matching?

[Oliver Kiddle]

--- Adam Spiers <adam@spiers.net> wrote:

> however the other two invocations are:
> 
>   ..... | perl -pe 's/%{.*?%}//g'

Does this do what you want:
... | sed 's/%{[^}]*%}//g'

It works here unless for some reason you have a closing curly bracket
in your escape sequence - assuming I've not missed something else. It
is fairly common to do [^..]* instead of .* when avoiding the effects
of greedy matching. What does the ? achieve in your perl regex?

It's a pity the col program isn't more powerful.

> They are done in order to strip control characters from a prompt so
> that its display width can be determined.  At first I thought that it
> would surely be easy to avoid this, but I still haven't come up with

I haven't looked at your prompt function but you might also consider
checking if you can get what you want with the ternary expression in
the prompt expansion as it can check how many characters have been
printed on the current line.

Oliver

____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie

Re: non-greedy matching?

[Bart Schaefer]

On Mar 21,  2:23pm, Adam Spiers wrote:
} Subject: non-greedy matching?
}
}   ..... | perl -pe 's/%{.*?%}//g'
} 
} They are done in order to strip control characters from a prompt so
} that its display width can be determined.

I had to do something similar in prompt_bart_setup, and ended up with
this:

	${#${(%%f)${PS1//[%]\{[^%]#%\}/}}[1]}

The (f) and [1] are because of the multi-line PS1, where it computes the
length only of the first line.  The above works as long as you don't
have other prompt escapes inside the %{ %}.  Hmm.  Perhaps this:

	${#${(%%)${prompt_line_1a//[%]\{([^%]|%[^\}])#%\}/}}}

Looking at prompt_adam2_precmd, it does exactly what prompt_bart_precmd
does: compute a padding width by subtracting from $COLUMNS.  With the
above expression you can get rid of prompt_line_1[ab]_no_color entirely:

	prompt_padding_size=$(( COLUMNS
		- ${#${(%%)${prompt_line_1a//[%]\{([^%]|%[^\}])#%\}/}}}
		- ${#${(%%)${prompt_line_1b//[%]\{([^%]|%[^\}])#%\}/}}} ))

Which also, as Sven mentioned, gets rid of $(print -P ...).

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   

Re: non-greedy matching?

[Oliver Kiddle]

--- Adam Spiers <adam@spiers.net> wrote: 
> Any ideas?  The only alternatives I've come up with are:
> 
>   foo=$(print -P "$prompt_string")
>   bar="${foo//^[[[0-9;]##m/}"

I should have thought about this before replying the first time but I
didn't until after Sven's e-mail. If you have extendedglob set, you can
do:
${(%%)${PS1//%\{(^*%\}*)%\}/}}
Doing the replace before the prompt expansion allows this to match the
%{...%} instead of the escape sequence. If you have any parameters
which when substituted include escape sequences, you may need to use
(e) before PS1 to expand these first. I trust this more than the sed
because it can do (^*%\}*) which matches anything which doesn't contain
%} to force the non-greedy behaviour.

Oliver

____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie