I'm coming over from total commander and there it has a limit of 32767 characters, which means about(?) 126 selected paths if they are all 255 chars per path. To counter this limitation, total commander has a token/argument called %L which stores a path to a .tmp file (which is a text file) with all the selected paths stored in that .tmp file.
My questions:
Does {allfilepath$} and it's comparable arguments have a similar limit?
If there is a limit, is there a way around it.
For context, my scripts which are put in buttons need {allfilepath$} and if there is limit with a workaround how can I use that workaround?
Windows has a command line limit, which affects all software.
You can work around it by putting the file list into a text file and passing just the name of the text file to the command. But only some commands support that. (Ones that often take a lot of filepaths, like archive tools, generally do support it.)
If applicable, you can also run the program once for each file instead of for all files at once. Using {filepath$} will do that automatically if more than one file is selected.
I forgot to mention: When tools support taking a file list via a text file, they usually have a special syntax for it.
(In other words, you can't just add |filem to {allfilepath$}. It'll need something else changed to tell the program to act on the list in the file, not the file itself.)
Exact details will depend on the tool that you're running.
