[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: tla-update-ids lacks support for filenames with

From: Miles Bader
Subject: Re: [Gnu-arch-users] Re: tla-update-ids lacks support for filenames with spaces
Date: Mon, 24 May 2004 13:58:43 -0400
User-agent: Mutt/1.3.28i

On Mon, May 24, 2004 at 07:42:01PM +0200, address@hidden wrote:
> > So, --slightly-escaped, escapes space, newline, tab, backslash, that's
> > it?
> $ tla escape "`echo -e 'foo bar\tbaz\\'`" ; echo
> foo\(sp)bar\(tab)baz\\

I'm not sure what you're trying to say here, I know those are the characters
that the current escaping code uses; what I want is for it to _only_ escape
those characters.  So if a filename is `hellow\243\133 world' (pretend those
`\...' sequences are actually chracters), I'll see `hellow\243\133\(sp)world'.

> Based on this you can make your own escaping engine in sed or such

Not if there can be \(U...) escapes -- those are pain to deal with even if
they're only 8 bits.

> you need to be aware that you are responsible for maintaining it when
> something in the tla encoding will be changed (unlikely but not
> impossible) and be gracefull if there are escapes that your simpler
> engine cannt handle.

That was my _whole point_ -- I don't want the possibly open-ended and
certainly annoying (can't parse it with regexp substitution) full escaping
langage, I want the raw filenames with only whitespace escaped (which can be
parsed with only [simple] regexp substitution).

Obviously I realize that I'd be responsible for keeping it up to date, but
then since it would have a fixed set of escapes -- space, backslash, newline
tab -- that would be unlikely to be a problem.

> Thats surely needed, but using the current solution is
> sematically correct and only affects performance.

Oh, how nice.

`To alcohol!  The cause of, and solution to,
 all of life's problems' --Homer J. Simpson

reply via email to

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