When passing the parent path, an extra quote is added to the argument.

[Mapaler]

When passing the parent path, an extra quote is added to the argument.

Set a button text.exe in the toolbar and the parameter is %P%S

Choose parent path (⇧..) and click the button.

The resulting path will be followed by an extra quotation mark.

Code: Select all

C:\Users\Mapaler\source\repos\SkyScan\Create User Folder\bin\Debug"

Image: https://imgur.la/image/1649-TotalCMD64-Total-Commander-%28x64%29-11.03-David-Attie.is63c

How to solve this problem?

[white]

If you add a question mark, you can see what is passed to the program.

Code: Select all

?%P%S

No extra quote is added, but when a folder contains a space, the argument will be in between quotes.
I assume your program cannot handle this and shows the error shown in your screenshot. If so, you can include %Q.

%Q Turn off automatic quotation marks around certain parameters like %P%N when the name contains a space. The user will then have to place them by himself.

[Mapaler]

This is indeed in line with the rules of Windows.
https://learn.microsoft.com/en-us/dotnet/api/system.environment.getcommandlineargs?view=net-9.0

This issue is caused by the Last Slash being passed to the path by Total Commander.

If I select a folder in the list, there will be no slash at the end of the path. However, if you select the parent path, there will be a slash at the end.
Image: https://imgur.la/image/Strip-2.isDM3

[white]

This issue is caused by the Last Slash being passed to the path by Total Commander.

And which program cannot handle that?

[Fla$her]

2Mapaler
I would have noticed that a long time ago. TC 11.03? Check on 11.51.

[Mapaler]

2Mapaler
I would have noticed that a long time ago. TC 11.03? Check on 11.51.

I've tested it and 11.51 still has this "bug".

And which program cannot handle that?

• .Net Framwork 4.8 And .Net 8
  Image: https://imgur.la/image/1655-TotalCMD64-Total-Commander-%28x64%29-11.03-David-Attie.iBraa
  Image: https://imgur.la/image/1656-TotalCMD64-Total-Commander-%28x64%29-11.03-David-Attie.iB63p

  Code: Select all

  static void Main(string[] args)
  {
       MessageBox.Show(String.Join(" ", args));
  }
  

• Visual Basic 6
  Image: https://imgur.la/image/1657-TotalCMD64-Total-Commander-%28x64%29-11.03-David-Attie.iBOSO
  There is no native support for parameter parsing, so you need to call the API.

  Code: Select all

  Private Declare Function GetCommandLineW Lib "kernel32" () As Long
  Private Declare Function CommandLineToArgvW Lib "shell32.dll" (ByVal lpCmdLine As Long, pNumArgs As Long) As Long
  Private Declare Sub CopyMemory Lib "kernel32" Alias "RtlMoveMemory" (Destination As Any, Source As Any, ByVal length As Long)
  Private Declare Function LocalFree Lib "kernel32" (ByVal hMem As Long) As Long
  Private Declare Function lstrlenW Lib "kernel32" (ByVal lpString As Long) As Long
  
  Function GetCommandLineArgs() As String()
      Dim ptrCmdLine As Long
      ptrCmdLine = GetCommandLineW()
      
      Dim numArgs As Long
      Dim ptrArgs As Long
      ptrArgs = CommandLineToArgvW(ptrCmdLine, numArgs)
      
      If ptrArgs = 0 Then Exit Function
      
      Dim args() As String
      ReDim args(numArgs - 1)
      
      Dim i As Long, ptrArg As Long
      For i = 0 To numArgs - 1
          CopyMemory ptrArg, ByVal ptrArgs + i * 4, 4
          args(i) = LPWSTRtoStr(ptrArg)
      Next i
      
      LocalFree ptrArgs
      GetCommandLineArgs = args
  End Function
  
  Function LPWSTRtoStr(ByVal ptr As Long) As String
      If ptr = 0 Then Exit Function
      Dim length As Long
      length = lstrlenW(ptr)
      LPWSTRtoStr = String$(length, 0)
      CopyMemory ByVal StrPtr(LPWSTRtoStr), ByVal ptr, length * 2
  End Function
  
  Sub Main()
      Dim cml, i
      cml = GetCommandLineArgs()
      For i = LBound(cml) To UBound(cml)
          MsgBox cml(i)
      Next
  End Sub

• Node.js
  Image: https://imgur.la/image/1660-WindowsTerminal-CProgram-Filesnodejsnode.exe.iBXE7

  Code: Select all

  console.log(process.argv);
  process.stdin.setRawMode(true);
  process.stdin.resume();
  process.stdin.on('data', process.exit.bind(process, 0));

• Python
  Image: https://imgur.la/image/1661-WindowsTerminal-CProgram-FilesWindowsAppsPythonSoftwareFoundation..iBlSF

  Code: Select all

  import sys
  import msvcrt
  args = sys.argv
  print(args)
  msvcrt.getch()

• Windows Script Host
  Image: https://imgur.la/image/1659-TotalCMD64-Total-Commander-%28x64%29-11.03-David-Attie.iB0ev

  Code: Select all

  for (var i = 0; i < WScript.Arguments.length; i++) {
    WScript.Echo(WScript.Arguments.item(i));
  }

Only WSH was able to get the final slash correctly, and all other languages I could use, were escaped as quotation marks.
I think any program that uses the CommandLineToArgv Win32API will have this problem, because that's the Windows parsing logic.

[Fla$her]

I've tested it and 11.51 still has this "bug".

Hmm. Is there a difference between x32 and x64?

[Mapaler]

Hmm. Is there a difference between x32 and x64?

This problem exists both x32 and x64.

[Mapaler]

I asked the AI and it told me

When passing a path with spaces via a parameter, you should not include a slash at the end.

Code: Select all

YourProgram.exe "C:\path to folder"

If you do need to include a slash, you should escape with two slashes.

Code: Select all

YourProgram.exe "C:\path to folder\\"

[Horst.Epp]

2Mapaler
It doesn't make sense to tell us what AI says, there is no AI knowing the real world.
TC has no problem with slash or no slash with such parameters.
You were asked to tell us what program has problems with it ?

[AntonyD]

https://ss64.com/nt/syntax-esc.html

Special Cases using backslash escape
To save a directory path with a trailing backslash (\) requires adding a second backslash to 'escape the escape'
so for example instead of "C:\My Docs\" use "C:\My Docs\\"

https://learn.microsoft.com/en-us/cpp/cpp/main-function-command-line-args?view=msvc-160#parsing-c-command-line-arguments

A double quote mark preceded by a backslash (") is interpreted as a literal double quote mark (").

https://users.rust-lang.org/t/interpret-the-path-enclosed-in-double-quotes-on-windows/38173/11
better read starting from "For example, the following is a quick summary of the behaviour on my Windows 10 box."

https://daviddeley.com/autohotkey/parameters/parameters.htm

[Mapaler]

2Horst.Epp

I use %P%S to pass the selected folder and include the path in quotation marks when there are spaces.

1. If you select a folder, there is no slash after the passed parameters;
2. When the parent directory is selected, there is a slash after the passed parameters.

When case 2, the parameters captured within the software end in quotation marks, which leads to parsing errors for the file path.

Image: https://imgur.la/image/1668-CreateUserFolder-%E5%88%9B%E5%BB%BA%E7%94%A8%E6%88%B7%E6%96%87%E4%BB%B6%E5%A4%B9.iBs95

[Fla$her]

2Mapaler
That is, this is not the problem of the TC, but of the application to which the path with the backslash is passed.

[white]

Hmm. Is there a difference between x32 and x64?

No, and it has been like this for a very long time.

%P causes the source path to be inserted into the command line, including a backslash (\) at the end.

When the parent entry ".." is selected, %S produces no result, leaving the path with a trailing backslash.

This is indeed in line with the rules of Windows.

I think any program that uses the CommandLineToArgv Win32API will have this problem, because that's the Windows parsing logic.

According to Windows rules, the way arguments are parsed is left entirely up to the program being launched. This makes it messy and inconsistent. Windows programs also don’t use a consistent way of parsing arguments. The CommandLineToArgvW API and similar functions in programming languages are just a possible way to implement basic argument parsing. They are not a Windows rule.

The parent entry in TC is handled in a special way. It sometimes means parent folder, and other times current folder. When %P is directly followed by %S, %N, or similar placeholders that turn out to be empty (when the parent entry is selected), it might be useful if TC would remove the trailing backslash from %P. Alternatively, it might be useful if TC would return the value ".." or "." for the %S, %N, or similar placeholders.

[Fla$her]

No, and it has been like this for a very long time.

At first, the problem was described in such a way that the path was passed only with a closing quotation mark after the backslash. Now it has become clear that this is not the case.