Jim Wright wrote:
what definition of regexp would you be following?
that's another degree of liberty. hrovje and i have chosen to integrate
in wget the GNU regex implementation, which allows the exploitation of
one of these different syntaxes:
RE_SYNTAX_EMACS
RE_SYNTAX_AWK
RE_SYNTAX_GNU_AWK
RE_SYNTAX_POSIX_AWK
RE_SYNTAX_GREP
RE_SYNTAX_EGREP
RE_SYNTAX_POSIX_EGREP
RE_SYNTAX_POSIX_BASIC
RE_SYNTAX_POSIX_MINIMAL_BASIC
RE_SYNTAX_POSIX_EXTENDED
RE_SYNTAX_POSIX_MINIMAL_EXTENDED
(see
http://cvs.savannah.gnu.org/viewcvs/emacs/emacs/src/regex.h?view=markup)
among these, i would probably go for a POSIX_EXTENDED syntax.
I'm not quite understanding the comment about the comma and needing
escaping for literal commas. this is true for any character in the
regexp language, so why the special concern for comma?
hrvoje already answered to this question.
I do like the [file|path|domain]: approach. very nice and flexible.
(and would be a huge help to one specific need I have!) I suggest also
including an "any" option as a shortcut for putting the same pattern in
all three options.
do you think the "any" option would be really useful? if so, could you
please give us an example?
--
Aequam memento rebus in arduis servare mentem...
Mauro Tortonesi http://www.tortonesi.com
University of Ferrara - Dept. of Eng. http://www.ing.unife.it
GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget
Deep Space 6 - IPv6 for Linux http://www.deepspace6.net
Ferrara Linux User Group http://www.ferrara.linux.it
