[Tcl-bugs] [SPAM] [Tcl] (sebres) tkt (Open): glob and file normalize inconsistencies on case insensitive filesystem

[<and...@gm...>]

Automated mail by fx, on behalf of and...@gm...

Ticket Change [72658b00bc025e6da56813714ef3746849e53bac118ac38ea32c279848ae40cb]
  [glob and file normalize inconsistencies on case insensitive filesystem]
  By      sebres
  For     Tcl
  On      2026-03-16T13:05:59.826
  Details https://core.tcl-lang.org/tcl/tinfo?name=72658b00bc025e6da56813714ef3746849e53bac118ac38ea32c279848ae40cb
  Ticket  https://core.tcl-lang.org/tcl/tktview/108904173c1a823a20823885c7b29ab536434a5a

Changed Fields
  closer:     nobody
  icomment:   Yes, the behavior is reasonable, if you'd forget the case-sensitivity
              thing (you trying persistently to consider case sensitivity there,
              where it does no matter).

              Regarding normalization from string and "correct" value, I guess one
              could indeed try to optimize it somehow (e. g. return translated path
              object instead of normalized path object from glob on windows, so that
              [file normalize] would be more "consistent" as for
              case-sensitivity)...

              What would be definitely worse to make such kind of implicit
              "normalization" for EVERY hit in the result of glob by default,
              because this can cause large performance degradation (by large
              directory listing), or issues like [02d5d65d70].
  login:      sebres
  resolution: None
  status:     Open

------------------------------------------------------------
See Tcl/Tk development @ http://core.tcl-lang.org/
------------------------------------------------------------