[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: |
Jan Hudec |
Subject: |
Re: [Gnu-arch-users] =tagging-method and non-portable filenames |
Date: |
Thu, 4 Sep 2003 08:44:02 +0200 |
User-agent: |
Mutt/1.5.4i |
On Wed, Sep 03, 2003 at 07:23:02 -0500, Joe Osborn wrote:
> Hello, List!
>
> I'm a Mac OS X developer doing revision control with Arch; I love it.
> It's the best software of its kind that I've seen outside of
> Smalltalk's changeset system, and it's only not that because it's
> language-agnostic, which is really fine, it can't be aware without
> being inflexible, and Smalltalk's system is a part of the image, etc ad
> infinitum.
>
> 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?
Space won't work thus far. It used to be forbiden because larch was
a shell script and is still explicitely forbiden in tla.
> This is equally not-working in larch and tla. Any suggestions?
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec
<address@hidden>