On 07/30/2011 06:28 PM, Laimis wrote:

> http://weitz.de/regex-coach/

EXE.
Ir PE, o ne ELF. Tiek jau to, gal ateityje pravers ;)

> Nors šiaip, tai klasės turėtų būti įvilktos į laužtinius. Tad:
> '\.[[:digit:]]{4}\.rvt$'
>
> ar net paprasčiau:
> '\.[0-9]{4}\.rvt$'

pasirodo ne.
http://lists.samba.org/archive/rsync/2002-November/004160.html

bet --rinclude --rexclude iki šiol MAN'e nepasirodė.

pagaliau prisiruošiau literatūros valandėlei ir ...

INCLUDE/EXCLUDE PATTERN RULES
        You can include and exclude files by specifying patterns using 
the "+", "-", etc. filter rules (as introduced in the FILTER RULES 
section above).  The  include/exclude  rules each specify a pattern that 
is matched against the names of the files that are going to be 
transferred.  These patterns can take several forms:

        o      if  the  pattern  starts with a / then it is anchored to 
a particular spot in the hierarchy of files, otherwise it is matched 
against the end of the pathname.  This is similar to a leading ^ in 
regular expressions.  Thus "/foo" would match a name of "foo" at either 
the "root of the transfer" (for a global rule) or in the merge-file’s 
directory  (for a per-directory rule).  An unqualified "foo" would match 
a name of "foo" anywhere in the tree because the algorithm is applied 
recursively from the top down; it behaves as if each path component gets 
a turn at being the end of the filename.  Even the unanchored "sub/foo" 
would match at any point in the hierarchy where a "foo" was found within 
a directory named "sub".  See the section on ANCHORING INCLUDE/EXCLUDE 
PATTERNS for a full discussion of how to specify a pattern that matches 
at the root of the transfer.

        o      if the pattern ends with a / then it will only match a 
directory, not a regular file, symlink, or device.

        o      rsync chooses between doing a simple string match and 
wildcard matching by checking if the pattern contains one of these three 
wildcard characters: ’*’, ’?’, and ’[’ .

        o      a ’*’ matches any path component, but it stops at slashes.

        o      use ’**’ to match anything, including slashes.

        o      a ’?’ matches any character except a slash (/).

        o      a ’[’ introduces a character class, such as [a-z] or 
[[:alpha:]].

        o      in a wildcard pattern, a backslash can be used to escape 
a wildcard character, but it is matched literally when no wildcards are 
present.

        o      if the pattern contains a / (not counting a trailing /) 
or a "**", then it is matched against the full pathname, including any 
leading  directories.  If  the  pattern doesn’t contain a / or a "**", 
then it is matched only against the final component of the filename. 
(Remember that the algorithm is applied recursively so "full file‐name" 
can actually be any portion of a path from the starting directory on down.)

        o      a trailing "dir_name/***" will match both the directory 
(as if "dir_name/" had been specified) and everything in the directory 
(as if  "dir_name/**"  had  been  specified).  This behavior was added 
in version 2.6.7.

-- 
Žiūrėkite,
kad rašto kas vaikų akims nebeatimtų