[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: Ethan Benson
Subject: Re: [Gnu-arch-users] =tagging-method and non-portable filenames
Date: Thu, 4 Sep 2003 00:28:49 -0800
User-agent: Mutt/1.3.28i

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

whitespace in filenames is absolutly forbidden in arch.  removing this
restriction is not at trivial as you think.  reference the list archives.

> 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?
> This is equally not-working in larch and tla.  Any suggestions?

rename your files to not include whitespace.

Ethan Benson

Attachment: pgp2Ri0zWidb4.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]