Trailing slash on {F}

Help & Support
1

Greetings Gurus, is there a way to get a trailing slash on folder names when using {F}?
Trailing slashes are on by default using {f}. Can it be enabled for {F}?

2

I think it works that way because {f} aka {filepath$} only returns a single path which sometimes also has a sub-folder/file name added on the end, while {F} aka {allfilepath$} returns multiple paths and doesn't make sense to add anything to (since it'd only be added to the last path, not all the others).

We also can't really change this now, as it would break existing buttons people are already using. (At least, we can't change the default. I guess we could add an argument to make it happen, but I don't think anyone else has ever asked for it in all the years it's been like this.)

If you need special formatting of paths which the {...} codes can't do built-in, scripting can do that fairly easily.

3

Thanks for the response, I'll explore the script option.

4

I want to do:

"C:\Apps\Windows Terminal\wt.exe" -d {sourcepath$}

This seems pretty simple, but fails because it runs (as shown by run with logging):

> C:\Apps\Windows Terminal\wt.exe -d "C:\Apps\Windows Terminal\"

Windows Terminal failure is:

Could not access starting directory "C:\Apps\Windows Terminal" "

The trailing slash on the folder escapes the surrounding quotes. This probably happens for ALL quoted folders and is probably never what the user wants.

EDIT: This fixes it (trailing slash becomes \\) but it's surprising this is needed:

"C:\Apps\Windows Terminal\wt.exe" -d {sourcepath$}\
5

If you setup Windows terminal as the default terminal, CLI DOSPROMPT should work.
As well as cmd.exe /s /k pushd "%V".

6

{sourcepath$|noterm} removes the trailing slash that confuses some command line tools when a quote comes after it.