Tcl Source Code

View Ticket
Ticket UUID: e83a97c7fee9d6bc2bec78d70b205a0e4d09ea8d
Title: windows: paths starting with tilde (~) are "partially" absolute
Type: Bug Version: any
Submitter: sebres Created on: 2019-11-08 13:23:56
Subsystem: 36. Pathname Management Assigned To: nobody
Priority: 5 Medium Severity: Minor
Status: Open Last Modified: 2019-11-08 13:30:37
Resolution: None Closed By: nobody
    Closed on:

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

Where glob already has correct behavior here:

% glob -directory e:/temp ~*
% glob e:/temp/~*
% cd e:/temp
% glob [pwd]/~*

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).