-
Additional comments to "special characters" and tilde expansion:
In 8.5.7 $,[,] is interpreted correct but the interaction between tilde is "strange".
=== 1: File: /net/pub/WinXP/test/~[filename].txt ===
[file exist $f]-> 0
[file type $f]-> could not read "/net/pub/WinXP/test/~[filename].txt": no such file or directory
[file type [file normalize $f]]-> file
[file type [subst...
2009-08-12 20:50:14 UTC in Tcl
-
Incorrect reference in 5.:
5. All interpreted special characters are commonly used on Windows, other than on Unix (c-shell style) - see topic 4.
should be changed to
5. All interpreted special characters are commonly used on Windows, other than on Unix (c-shell style) - see topic 6.
2009-08-09 13:07:22 UTC in Tcl
-
Tcl version: 8.5.7, also tested on 8.5.4, 8.5.5 with different behaviour
OS plattforms: Linux (ia32, amd64), Windows XP Professional
Problem Behaviour:
1. Depending on Tcl-version the "special" characters ($,[,],\,~) are interpreted different and incorrect.
2. Incorrect interpretation of "~" character, only meaningfull at beginning of a filename not on full path or inside of a filename...
2009-08-09 12:57:55 UTC in Tcl
-
As I want to retire from developing the ObexTool I'm asking if someone is willinig to continue this project.
If someone wants to contniue the development I will make him a maintaner and I will remove my account.
Please contact me via
gerhard(dot)reithofer(at)tech-edv(dot)co(dot)at
The sourceforge mail address is not read anymore.
2009-07-14 10:08:32 UTC in ObexTool
-
In some error situations the return value of tar::* functions are not initialized which leads to a runtime error when returning "return $ret".
2009-04-16 06:10:15 UTC in tcllib
-
Feature implemented in version 0.35.
New configuration parameter: preserve,filedate.
2009-01-03 18:09:26 UTC in ObexTool
-
exgerhardr added the obextool-0.35.tar.gz file.
2009-01-03 00:20:44 UTC in ObexTool
-
exgerhardr created the obextool-0.35 file release.
2009-01-03 00:17:22 UTC in ObexTool
-
Files larger than 2GB lead to invalid negative file offsets because the zip header entries are interpreted signed (scan format code "i").
The patch zip-1.0.1.tm.patch changes all file size related binary scan codes "i" to unsigned "iu".
I don't know if the CRC32 word is interpreted correct with "i".
2009-01-01 19:40:43 UTC in TclVfs
-
Trying to list a 8 GB zip file containing several 2GB files leads to:
error during seek on "file5": invalid argument
while executing
"::zip::open [::file normalize $zipfile]"
(procedure "vfs::zip::Mount" line 2)
invoked from within
"vfs::zip::Mount $inpfile ZIP"
invoked from within
"set fd [vfs::zip::Mount $inpfile ZIP]"
(file "./list_zip.tcl" line 101...
2008-12-30 18:47:34 UTC in TclVfs
