on Thursday 21 January 2010 Stephen Dowdy wrote:
and the value in the <match> element doesn't even have any regex pattern, wildcard, classes, etc.
From this example, all i can infer is that a <match> element value is used as a non-anchored match string. ("match anywhere")
I have seen another example showing the use of the "^" begin-of-line anchor symbol
e.g. "<match>^SUSE Linux Enterprise Server</match>".
But what is the full-extent of what i can use here?
it's a simple bash "=~" if [[ "uwe gansert" =~ u.e\ g[abc]ns ]]; then echo jo; fi but while looking at the code a few minutes ago, I noticed a bug in it :( Currently only substring matching seems to work properly which is what I used for testing the code when I implemented it :-/ I have to test that but by looking at the code, it looks like a bug -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org