[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] =tagging-method and non-portable filenames
From: |
Andrew Suffield |
Subject: |
Re: [Gnu-arch-users] =tagging-method and non-portable filenames |
Date: |
Thu, 4 Sep 2003 10:02:46 +0100 |
User-agent: |
Mutt/1.5.4i |
On Wed, Sep 03, 2003 at 07:23:02AM -0500, Joe Osborn wrote:
> I'm running into a problem, however, which is inconveniencing me. Some
> changes I make to =tagging-method's regexen for the different file
> types(Excluded, Precious, Junk, Backup) are effective and tla inventory
> will give me a proper list by the types given. However, changes to
> Unrecognized do nothing, and Source seems ineffective too. While it
> may be I'm writing bad regex, my goal is to allow non-portable file
> names, as a lot of mine are, to be put under version control as
> sources. The following line:
>
> source ^([_=a-zA-Z0-9[:space:][:punct:]].*)$
>
> is either malformed or ineffective. Which is it? File names like "3rd
> Edition, Revised" and "Ice Age" still fall into the Unrecognized
> section with this regex, even though
>
> find . [_=a-zA-Z0-9[:space:][:punct:]].*
>
> works fine. Is the limitation on the usage of non-portable file names
> a basic assumption of Arch? Is there a workaround? Am I just a fool?
There's a hardcoded set of characters which are allowed in filenames
(not "portable", but "characters Tom doesn't like people using in
filenames"). Spaces aren't included.
--
.''`. ** Debian GNU/Linux ** | Andrew Suffield
: :' : http://www.debian.org/ |
`. `' |
`- -><- |
pgp5GN9hFD4zV.pgp
Description: PGP signature