2
Fla$her 2
sqa_wizard 2
white
First of all, thank you all for your replies — I’ve learned quite a lot from the discussion.
Regarding the log file naming:
Code: Select all
/LOG+:C:\OneDrive\Logs\TENDER_%|DATE:~-4,4|%|DATE:~-7,2|%|DATE:~-10,2|.log
I have been using this format since Nov 2024, from TC 11.50 up to 11.57 final (including all intermediate beta versions), and it has been working fine.
That said, the following version you suggested is indeed cleaner and more concise — I wasn’t aware this syntax could be used in this way, so thanks for pointing it out:
Code: Select all
/LOG+:C:\OneDrive\Logs\TENDER_%|$DATE:YMD|.log
Regarding this point:
The second mistake is that param=%A is not used here for em_RoboCopy.
I’m not sure I fully understand this comment, as I don’t see param=%A used anywhere in my configuration. Could you please clarify?
About using em_RoboCopy:
Moreover, I don't see a practical advantage in using em_RoboCopy instead of %COMSPEC% /K ROBOCOPY. The savings here are minimal, while an unnecessary layer is used.
Yes, I agree this additional layer is not strictly necessary. The main reason I use em_RoboCopy is to assign a custom icon in the Start menu, so I can locate the command more quickly.
Regarding the mismatch between user commands and Start menu entries:
Obviously the user commands are not matching to the start menu entries.
parameter 1 sends commands to em_CMD. Note: em_CMD does not process any command (/K or /C) but starts a program (Start /D)
Yes, that is intentional. I use Start /D "%P" as a generic launcher for other commands as well, and I append & Pause in the parameter to keep the window open when needed.
Which versions exactly?
Concerning your "Eye Protection Mode" start menu entry:
"@echo" is not a command you can start. Move the parameters to the command field and it will work.
Did you move the parameters?
If it worked before, in which TC version?
I have been using this command since Nov 2024, across TC 11.50 up to 11.57 (including beta versions), and it was working in my setup.
I understand that placing content in the "command" field vs the "parameters" field behaves differently. My reasons for using the parameter field are:
1. Insert environment variable envvar in the parameters field. Using %envvar% directly isn't possible, because the % sign is already used for placeholders. Therefore this modified syntax needs to be used. The "command" field still uses the normal %envvar% field. (when I start to use this command, this function is not available yet if I am not wrong)
2. The presence or absence of parameters affects how icons are displayed in the TC Start menu, which also influenced my setup.
Moderator message from: white » 2026-05-21, 13:25 UTC
Replaced some code markup codes with quote markup codes to keep it readable for users.