DosTips.com

Batch syntax is extremely poor and doesn't support more complicated conditions.
You could try Conditionals on steroids which enables more benefits.

Also (in addition to dbeham's suggestion) the wsx tool can help you to get the required result: wsx /n /e:"m=LINE.match(/^outbox\/logs\/.*?(\d+)\.log$/)||next();n=Number(m[1]);if(n>max){max=n;str=LINE}" /begin:"str='';max=0" /end:"echo(str)" test.txt wsx /n /e:"m=LINE.match(/^outbox\/logs\/.*?(\d+)\...

Replace this one: with:

It could something like this: sed "s/></>\n</g" | sed "/<desc>.*<\/desc>/d; /<desc>/,/<\/desc>/d" Some explanation: 1. the first SED walks over all >< and inserts new line character \n between angle brackets 2. the second SED does two actions: 2.1 remove all lines having <desc> something </desc> 2.2...

As I said early If both <desc> and </desc> could be on the same line or on the same line with other tags you need something much more complicated There is workaround: sed "place each <desc> and </desc> completely to the separate lines" | sed "/<desc>/,/<\/desc>/d" You need only to invent this algor...

Assuming that the both <desc> and </desc> live alone in different lines (not in one line together), you can use the following command: sed "/<desc>/,/<\/desc>/d" If both <desc> and </desc> could be on the same line or on the same line with other tags you need something much more complicated. I hope ...

I am not sure that anyone can help you with no knowing about your SW environment.

Updates came to the first post. The tool version is the same but description is extended.

DESCRIPTION Times ago I invented the tool PSUBST being the extended version for the standard SUBST . Both tools allow to associate some paths with virtual drives. So executing the following command we have ability to achieve the particular path in two ways by the path itself and/or by the drive: su...

Functionality of clipboardData and its method setData is strongly restricted by MSIE. Indeed, try using clip.

I see your point. I need to step back and try to explain everything clearly as much as possible. I'll come back with the updated version of the tool in the first post.

For long time (I don't know exactly since when) Windows is already shipped with the "clip" tool: C:\>clip /? CLIP Description: Redirects output of command line tools to the Windows clipboard. This text output can then be pasted into other programs. Parameter List: /? Displays this help message. Exam...

As you can find -- everything is optional. If you enter an one line program, everything after is assumed as a file for processing. Each argument is opened as a file and processed line by line until EOF. wsx /n /e:"..." file1 file2 ... Otherwise. If you don't enter one line programs, the first item o...

to have a switch for the input and output Not agree. Additional switches make usage more complicated. But this is not fully your issue -- I think it is on my side in majority of cases because I can't immediately give complete and/or comprehensive explanation. In my vision the good tool is a pipe co...

No problem. Asking question is OK. They help to improve description. Let me know about the issues you experienced, if they have occurred.