gnu-arch-users
[Top][All Lists]
Advanced

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

[Gnu-arch-users] ANNOUNCE: Spaces in filenames, finished


From: chth
Subject: [Gnu-arch-users] ANNOUNCE: Spaces in filenames, finished
Date: Sun, 14 Mar 2004 20:01:33 +0100

The 'escaping' support is finished and a release is available at:

Name : address@hidden
Mirror: http://mirrors.sourcecontrol.net/address@hidden
Home : http://cehteh.homeunix.org/arch/address@hidden
buildcfg: pipapo.org/pika-escapes.tla

This release is in sync with the offical tla1.2 and will be merged into
1.3 soon (reminder for Tom ;)).

Note about the changes:

tla uses (pika) escaped filenames from now on. For every command which
spits out informationm uses escaping by default too! Many (if not all)
commands have a --unescaped option to turn escaping for information on
the console off (please notify me if I missed something).
The changes are backward compatible and only new archives which contain
files which wheren't allowed before will confuse older tla versions.
ChangLogs are always escaped, that can't be turned off.


Example:
The common shell sequence
tla tree-lint -t | while read file;
  do tla add $file;
done

should be rewritten as
tla tree-lint -t --unescaped | while read file;
  do tla add "$file";
done

or (see later)
tla tree-lint -t | while read file;
  do tla add "$(tla escape --unescaped "$file")";
done


ATTENTION FOR EXTERNAL TLA TOOL MAINTAINERS AND USERS!

escaping will likely break any tool which is not aware of it (that is
still backwards compatible, but new, formerly not allowed filenames will
confuse such tools now. You need to update this tools!!)

How to do it?
If you use hackerlab: Just head out for the new escaping engine there
and use it.

If you use scripting languages: there is a new 'escape' command to help
the whimps who can't call the Hackerlab functions

> echo "$(tla escape "foo bar")"
foo\(sp)bar

> echo "$(tla escape --unescaped "foo\\(sp)bar")"
foo bar

note that it only does escaping/unescaping in an authorative manner but
does not add a newline or does any other thing with the string, hence
the echo here.


        Christian


PS: Thanks Lindows.com for funding the development




reply via email to

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