Tcl Source Code

Ticket Change Details
Login
Overview

Artifact ID: 3d3271ca51422e3ce3c9d1ac47b9ff26d843b2045b58b3955e123f24cd719068
Ticket: e83a97c7fee9d6bc2bec78d70b205a0e4d09ea8d
windows: paths starting with tilde (~) are "partially" absolute
User & Date: sebres 2019-11-08 13:30:37
Changes

  1. Change comment to:

    Issue could be considered as continuation of [9e6b569963]...

    Note the ticket is only about ~* and not ~/* (which could be firstly considered as rather absolute path).

    Under windows it is possible to have relative paths (file and directory names) starting with tilde, as such it is "partially absolute" path, so in my opinion should be interpreted as relative if used in file join.
    From this point of view file join $dirname $filename behaves incorrectly under windows if filename starting with ~ characters:

    % file join $env(tmp) ~*
    ~*
    % file join $env(tmp) ~abc.txt
    ~abc.txt
    

    Where glob already has correct behavior here:

    % glob -directory e:/temp ~*
    e:/temp/~abc.txt
    % glob e:/temp/~*
    e:/temp/~abc.txt
    % cd e:/temp
    % glob [pwd]/~*
    E:/Temp/~abc.txt
    

    Just this one is a bit confusing (I know it is a bit "ambiguous", but...):

    % glob ~*
    user "*" doesn't exist
    
    Despite ambiguity it looks still weird to me:
    1. either the decision remains "path of pattern is absolute", it could be fixed to list all users/homes where caller is permitted.
    2. or the decision going either to "path of pattern considered as relative" under windows, it should behave like glob [pwd]/~* (so find all files starting with "~" in current directory).

    Anyway (after fix) it could be additionally documented (with difference between unix/windows).

  2. Change login to "sebres"
  3. Change mimetype to "text/plain"