Ok, I modified eas command:A) you should add a command like "<aesName" to define it from VP.
Code: Select all
eas {<autoupdate_script_name>|<mask>}
You may execute any internal file using <exec command. If this internal command pointed to physical application, it will be launched with passed parameters. So, if you have some little tool that launches any process, you may add it to VP and start any external process with it (e.g. cmd.exe or link to it that will be started minimized, or any tool w/o console window).B) could you add also a way to execute external prog from script "<do ....... "?
I have no access to selection, TC doesn't provide such interface. I hope Ghisler will implement launching internal FS files from button bar etc - then you would use %L, %S, %L and all other functions (it was suggested here).C) could you also have internal variables like TC's %F %S and why not a %L
How do you see it? This command takes lines from files, takes filenames from it and adds to VP under that names. Script text have no name, so it can't be used with <put command.D) could you also support importing script entries with the put /l command ?
You may use <edit command - it allows to copy/paste script text. Also you may edit scripts directly in state file - even more, you may save state with just one file, edit it to correct script and load it back to current virtual folder (or make some stub with single state file line for script creation). Also you may write script in editor and then use <add command with pasted text to make script file.I think it could be more convenient to prepare and save script in an editor than typing in the command bar.
If you need %L etc now, you may start external tools that will get selection from TC panel.