[TC11.55rc1-rc4] Command chain does not work with cd

[sa16]

The chain of commands does not work, for example, in the TC folder:

Code: Select all

TOTALCMD#BAR#DATA
cm_ClearAll,cd "History.txt"

WCMICONS.DLL

[ghisler(Author)]

Chained commands work in the command line, but not with the cd command, this isn't currently supported.

Moderator message from: ghisler(Author) » 2025-05-27, 13:04 UTC

Moved to suggestions

[sa16]

this isn't currently supported.

In the TC11.02... TC11.51 chains worked.
Perhaps after this fix:

05.10.23 Release Total Commander 11.02 release candidate 1
...
11.09.23 Fixed: cd *.ext or cd c:\path\*.ext didn't work in command line, or when combining multiple commands in button bar (where the path must be put in double quotes) (32/64)

[petermad]

2ghisler(Author)
Obviously sa16 is not talking about the command line, but about using cd chained in a button.

2sa16
If works in a button if you use:

Code: Select all

[Configuration]
IgnoreDirErrors=1

in your wincmd.ini file.

2ghisler(Author)
I think it is a bug that it is now necessary to use IgnoreDirErrors=1 to make cm_ClearAll,cd "History.txt" work in a button?

[tuska]

Hmm, here's another example where the button works.

Code: Select all

TOTALCMD#BAR#DATA
cd "*.txt",cm_SelectAll

wcmicons.dll,9
cd "*.txt",cm_SelectAll|https://www.ghisler.ch/board/viewtopic.php?t=85897|[TC11.55rc1-rc4] Command chain does not work with cd|cm_ClearAll,cd "History.txt"


-1

[petermad]

In the TC11.02... TC11.51 chains worked.

I can confirm that it worked in a button (like the one in the first post) in TC11.51 without the IgnoreDirErrors=1 parameter.

Moderator message from: petermad » 2025-05-27, 13:38 UTC

Moved from "TC fixed bugs" back to "TC11.x bug reports (English)"

[sa16]

2tuska
To demonstrate the bug, an example is given in which an error appears, and not vice versa.
Use an absolute path or "%COMMANDER_PATH%\History.txt" - there will be no error either.

[petermad]

2sa16

I can confirm that it works when using cd "%COMMANDER_PATH%\History.txt" instead of just cd "History.txt" - where if History.txt is present in the current directory.

And still - it worked with cd "History.txt" in TC 11.51 - so TC 11.55 is currently not backwards compatible in this matter.

[tuska]

2tuska
To demonstrate the bug, an example is given in which an error appears, and not vice versa.

Please excuse my unfortunate choice of words.

I gave this example to refute this statement:

Chained commands work in the command line, but not with the cd command, this isn't currently supported.

[sa16]

2tuska
Now I get it! Excuse me too!

[ghisler(Author)]

Thanks, I understand the problem now. It's caused by the unfortunate change to support commands like this:
cd "test 1.*" "test 2.*"
To support this, I can no longer just remove the first double quotes, I have to remove them wherever needed. But this clashes with chained commands, where the parameters of cd must be always in double quotes, otherwise it would be impossible to find the end of a cd command. Because of this change, cd "History.txt" is passed with the double quotes to the cd command handler, which fails.

[petermad]

2ghisler(Author)

Is it because of the backslash in the name that it still works for cd "%COMMANDER_PATH%\History.txt" or cd "c:\totalcmd\History.txt" ?

[JOUBE]

Thanks, I understand the problem now. It's caused by the unfortunate change to support commands like this:
cd "test 1.*" "test 2.*"
To support this, I can no longer just remove the first double quotes, I have to remove them wherever needed. But this clashes with chained commands, where the parameters of cd must be always in double quotes, otherwise it would be impossible to find the end of a cd command. Because of this change, cd "History.txt" is passed with the double quotes to the cd command handler, which fails.

This is really annoying. Please just remove the change and everything will be fine again. Why do a customer keep making more and more pointless demands and, above all, "Ghisler Software GmbH" follow them? Please put such requests to "will not be changed" and stop answering at the subforumIn the interest of your professional customers who do not want to take steps backwards.

[ghisler(Author)]

Please just remove the change and everything will be fine again.

Why such radical negativity? I just need to address this additional special case.

[sa16]

27.05.25 Fixed: Command cd "filename" to position cursor on file could no longer be combined with other commands on a button (32/64)

Confirmed fixed in TC 11.55rc5.