DosTips.com

I'm curious what the behavior is with XP (or any other version). Windows XP pro, 32 bit, Version 5.1.2600, just terminates the execution of the batch ater the first performed test (same behaviour for all tests): ----------------------------------------------- :test1 Die eingegebene Zeile ist zu lan...

At the beginning of the test the behavior is different than later, and the original behavior can't be reset by closing cmd.exe. I can reset it only by restarting the computer. The changes are relevant for the size of lines and if they throw an error or not. In the beginning my lines can be very lon...

The 8191 character size limit is pervasive throughout cmd.exe batch parsing. There are many buffers in the various phases, each one limited to 8191 bytes. I wanted to investigate how each "phase" handles an overflow of the buffer. I know sometimes it creates an error, sometimes the data is truncated...

It wouldn't be hard to write a custom JScript or VBScript solution. I went ahead and developed a JREPL.BAT solution - it is significantly faster than any pure batch solution once the input becomes "large". I used line continuation just to make it easier to read. jrepl "^outbox/logs/.*?(\d+)\.log$"^ ...

Your way of dealing with dates is not good as it depends on the locale settings for the computer. For example, %date% on my machine yields Fri 03/13/2020 which completely breaks your code. You should be using FOR /F with WMIC OS GET LOCALDATETIME to get the date and/or time in a way that can be par...

FYI - No need to create a separate topic when this last question is obviously related to the previous. The ; at the end of the statement is causing the problem. SET /A sort of is expecting a second computation, although the proper symbol to use for multiple computations is a comma. Remove the semico...

SET /A is the one case where you don't need delayed expansion because SET /A can expand variables directly - there is no need to use % or ! expansion. set /a "result=result*2" :: or better yet set /a "result*=2" But why do you initially set result to 8 in the first place? why not set /a "result=8*2"...

The above post is a follow-up question to my StackOverflow answer to this question . Based on the OP's last comment on 2020-03-11 , the solution is to escape the quotes and backslashes as \" and \\ when using Webpack ShellPlugin: call "./framework/config/JREPL.BAT" \"(Error)\\(([\\c()]*|\\(([\\c()]*...

Please note that windows uses \ in paths, not / Also, you should learn to use the markup language supported by this site - html does not work. The buttons at the top of the post editor work well, and are pretty self-evident. The following one liner should do the trick from the command line for /r "c...

You must have named your batch script choice.bat or choice.cmd, so your script is calling itself instead of executing the CHOICE command. Rename your script to something else.

You should never name a script the same as an existing command.


Dave Benham

A JREPL solution without the /M option (no size limit as long as no line approaches 1 GB) can be done in 3 steps (assuming all <desc> and </desc> are paired properly): :: Remove all <desc>...</desc> blocks within one line call jrepl "<desc>.*?</desc>" "" /f "input.xml|utf-8" /o - :: Remove all lines...

Note - XML CDATA and/or comments containing <desc> or </desc> are likely to break any regular expression based solution. Regular expressions should generally not be used to parse or manipulate XML unless you are confident in the physical layout of the XML file.

As a work-around, I'll just install Perl and run a one-liner. Another option is to use my JREPL.BAT regular expression file processing utility . It is pure script (hybrid JScript/batch) that runs natively on any any Windows version from XP onward, without the need of any 3rd party exe or dll file. ...

Here is JREPL version 8.5 JREPL8.5.zip Summary of Changes 2020-02-29 v8.5: Added /EOL option to set the end of line terminator. Added the eol global jscript variable. Doc fix - No EOL if /RTN option specifies a :LineNumber. . . . New /EOL option /EOL EndOfLineString Write lines using EndOfLineStrin...

Your problem is grep and cmd.exe have different quoting and escape rules. You need to account for both, remembering that cmd.exe quoting/escaping is processed before grep. cmd.exe does not have a mechanism to escape a double quote within a double quoted string. Once quoting has begun, the next quote...