Hello Vince!
Thanks very much for this, I can use this as a workaround as there is only one 'version' attribute in the XML document that I'm parsing. I suspect that the reason this is working is because the @XMLGETATTR function is operating on the root node by default when the filename is...
Hello
I have an XML file with the following structure
<Connect version='1.0'>
<!-- ... -->
</Connect>
Prior to v28, I was using the following to retrieve the value of the 'version' attribute:
ECHO %@XMLXPATH["test.xml",/Connect/@version]
However, in v28 TCC is returning an error:
TCC...
If anyone else falls foul of this problem, you can work around it by piping the resulting file through the TPIPE command, using the option to remove binary characters.
In my case, I was piping the output from Perforce's P4 command to both the screen and a temporary file, and then using the FIND...
Hello
The TEE command seems to be appending a null character to the text that it appends to the output files. I first noticed this with TCC 26.01.38, and the behaviour is still present in TCC 26.01.39
For example, executing this and then viewing the output file in something like NotePad++ will...
Hello
Please would you consider adding one or more commands and functions to perform certificate validation? For example:
CERT filename.ext
This command would show the certificate details for the file or files given to it, and could include options to check the revocation status and show...
Hello !
I've updated to Take Command v25 from v22, and the behaviour of the FOR command with the /a:d option seems to have either changed or is broken.
In v22, the following command will list the names of all of the subdirectories within the current directory:
for /a:d %a in (*.*) do...
Hello all
I checked my TCMD.INI as per Rex's suggestion, and there was no setting for DuplicateBugs. Adding DuplicateBugs=No to the [4NT] section of this file has resolved the problem.
Thanks very much to all of you for your help with this.
Chris
Hello Charles
Apologies, I only replied to the first part of your comment yesterday. I will most likely adapt the batch file to use DO instead of FOR, but this is a previously-working script that I just happened to run for the first time with TC 18 the other day. I think I previously wrote it...
Hello Vince
Which version of Take Command / TCC are you using? I am using version 18, and experiencing this problem. With version 13, the batch file works as expected.
Chris
Hello Charles
It's not the actual batch file that I was executing. It's a stripped-down example to illustrate the problem, with a hard-coded test that's always false.
Basically, if the FOR / DO loop contains an IF or IFF statement that evaluates to false, TCC seems to be bailing out of the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.