[11.50b1] Serious warning: 11.50b1 leaves the operating system fundamentals

The behaviour described in the bug report is either by design, or would be far too complex/time-consuming to be changed

Moderators: Hacker, petermad, Stefan2, white

Post Reply
JOUBE
Power Member
Power Member
Posts: 1685
Joined: 2004-07-08, 08:58 UTC

[11.50b1] Serious warning: 11.50b1 leaves the operating system fundamentals

Post by *JOUBE »

[11.50b1] Serious warning: 11.50b1 leaves the operating system fundamentals:

.\ as a reference to the current directory is no longer supported in exclusions in the sync tool (and where else?). *)

This is an exit from compatibility with the operating system.

JO"So no one can longer use the Tc seriously."UBE

*) Example: *.* | .\Folder\
Additional hint: .\Folder\ is not Folder\ and not \Folder\
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 50824
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: [11.50b1] Serious warning: 11.50b1 leaves the operating system fundamentals

Post by *ghisler(Author) »

This has never been supported officially. Why not use
*.* | \Folder\
instead? This would exclude folders relative to the start path.

Moderator message from: ghisler(Author) » 2024-10-15, 10:37 UTC

Moved to will not be changed
Author of Total Commander
https://www.ghisler.com
JOUBE
Power Member
Power Member
Posts: 1685
Joined: 2004-07-08, 08:58 UTC

Re: [11.50b1] Serious warning: 11.50b1 leaves the operating system fundamentals

Post by *JOUBE »

ghisler(Author) wrote: 2024-10-14, 15:57 UTC This has never been supported officially.
What is the point of this statement? The variant that is no longer supported is the normal path specification of a relative path and is of course officially supported by the operating system. If TC no longer supports this after years, that is a serious departure from the operating system. Or does the TC now determine how paths are to be specified in Windows?
ghisler(Author) wrote: 2024-10-14, 15:57 UTC Why not use *.* | \Folder\
instead? This would exclude folders relative to the start path.
This works, but is

- illogical: a path that begins with a \ is always related to the root directory under Windows (and with a / under Unix/Linux too).
- It is a departure from the procedure that has been in place in TC for years.
- It remains unclear why this was changed.

It is and remains a mistake to change it and should be changed back to the previous behavior.

It is a bug, even if apparently no one else here knows simple paths or does not use the TC extented.

2ghisler(author)
Change this back to previous behavior.
Please explain why this was changed (or is this just a side effect?)
Postponing it with the comment "will not be changed" is very strange, because it is currently being changed in the beta.

Joube
Post Reply