This mail is an automated notification from the bugs tracker
of the project: xtla.el.
/**************************************************************************/
[bugs #763] Latest Modifications:
Changes by:
Matthieu MOY <[EMAIL PROTECTED]>
'Date:
Mon 10/11/2004 at 16:09 (Europe/Paris)
What | Removed | Added
---------------------------------------------------------------------------
Resolution | None | Fixed
Status | Open | Closed
Fixed Release | | [EMAIL PROTECTED]
------------------ Additional Follow-up Comments ----------------------------
This should work now, but hasn't been heavily tested.
/**************************************************************************/
[bugs #763] Full Item Snapshot:
URL: <http://gna.org/bugs/?func=detailitem&item_id=763>
Project: xtla.el
Submitted by: Matthieu MOY
On: Mon 09/20/2004 at 22:34
Category: xtla.el
Priority: 5 - Normal
Resolution: Fixed
Assigned to: None
Originator Email:
Status: Closed
Planned Release: 1.0
Type of request: small bug
Fixed Release: [EMAIL PROTECTED]
Test case in xtla-tests.el:
Summary: xtla doesn't manage spaces/special characters in filenames
Original Submission: Since tla 1.2.1, it is possible to use special characters
like spaces in filenames. The output of tla commands is escaped like this:
$ tla tree-lint
These files would be source but lack inventory ids (`tla add' or a tagline
perhaps?):
foo(sp)bar
But the filenames should be given unescaped for tla arguments:
$ tla add 'foo bar'
To manage this in xtla, we have to
1) detect whether the current tla version manages spaces in filenames.
2) (defun tla-unescape (filename) ...) using "tla escape --unescaped"
3) Each tla output parser must unescape the filenames, and the unescaped
filenames must be stored in the ewoc lists.
4) Fix the bugs introduced by 1, 2 and 3 ;-)
The big question is: Should we try to manage this before the 1.0 version?
Follow-up Comments
------------------
-------------------------------------------------------
Date: Mon 10/11/2004 at 16:09 By: Matthieu MOY <moy>
This should work now, but hasn't been heavily tested.
For detailed info, follow this link:
<http://gna.org/bugs/?func=detailitem&item_id=763>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
