http://www.ghisler.ch/wiki/index.php/Unified_Parameters_System
It would be very nice to have it implemented.
Waiting for your suggestions and comments.

Moderators: Hacker, petermad, Stefan2, white
Maybe I've misunderstood you, but how all this can be done? I know only one way - macroses, but even macroses can't make absolutely the same things. For example, to take the list of the selected files on the inactive panel, the macros should either use clipboard (with replacing its current content), or call cm_SaveSelection (that causes additional dialogs to appear and disappear)... Both ways are inconvenient.Everything noted in this article is just a shortcut for something that can already be done.
This can be done: with %@ template.- start a program with a list of files as parameter
This can't.- multiple instances of a program with a single file.
Thanks I must have missed that. Fine!This can be done: with %@ template.
Well when a user adds such a parameter he always has to know the meaning of such a parameter so I don't see the problem here.Of course, in principle it's possible that on some template (e.g. %#) TC will start several program instances with the parameters specified, but it looks too off the rails. Currently (and in suggested improvement) all the templates are designed so that TC start a program with the list of parameters specified, and some user may think this is always true; so starting several instances instead of one will be a great surprise too him (maybe, very unlike one).
It's not regular?However, the current system of these templates is far from perfect: it is not regular
Why do I need an extra parameters for this? A trailing backslash is just a static character.%S stands for the source path without the trailing backslash (\) (this is the difference with %P).
A bit complicated but okay.Extended template %L
I don't see the usefullness here.New template %C
Full support!New template %@
8.3 is not really an encoding. I guess something else is intended here.Group 2 (encoding)
I meant that when all the parameters cause TC to start a single program instance with a set of parameters, and only one single template that cause it to start several instances, it may be confusing. But this is only MHO.Lefteous wrote:Well when a user adds such a parameter he always has to know the meaning of such a parameter so I don't the problem here.
No, it is not. For example, how can one suggest that %P on the opposite panel is %T? that %N on the opposite panel is %M? What is the idea of these letters in particular? In the suggested system all this is more regular. You know, for example, that for any template you may add the "!" prefix and it will be the same template but for the opposite panel.Some more detailed comments:It's not regular?However, the current system of these templates is far from perfect: it is not regular
Yes, it's a static character. But how could you remove it if it is not needed? For example, suggest that some program needs the name of the folder without the trailing backslash (and does not work if the backslash is present). What is one supposed to do without the %S template?Why do I need an extra parameters for this? A trailing backslash is just a static character.%S stands for the source path without the trailing backslash (\) (this is the difference with %P).
I personally don't see it too, but this may be of use for some case. I don't think that I'm able to foresee all the possible situations at once.I don't see the usefullness here.New template %C
Yes, maybe not very good name for the group... I meant that the Group 2 controls the way the file names are written into the file: full names, or short names, or Unicode-formatted names.Group 2 (encoding)[(quote]
8.3 is not really an encoding. I guess something else is intended here.
Not necessarily. Third way you haven't mention - global variables in script. Most (perhaps everything) of your proposals can be implemented right now with PowerPro or some similar (or more powerful) scripting language.macros should either use clipboard (with replacing its current content), or call cm_SaveSelection