Also on SS64 is the undocumented /UNI-OUTPUT (or /U) that outputs in unicode (UTF16), available since Win 7. I did not know about that one either, though it is not of much interest to me.
As I just learned at https://www.dostips.com/forum/viewtopic.php?f=3&t=9923&p=63727#p63726, SORT supports the /UNIQUE option, at least on Windows 10 :!: :D The built in help makes no mention of it, so it is no wonder that I've never seen this behavior before. Has anyone ever run across this option b...
OMG :shock: :!: :!: :!: :!: The standard Windows SORT command supports the /UNIQUE option, at least on Win 10, even though it is not documented - I had no idea :!: D:\test>sort /? SORT [/R] [/+n] [/M kilobytes] [/L locale] [/REC recordbytes] [[drive1:][path1]filename1] [/T [drive2:][path2]] [/O [dri...
Thanks Compo (and Carlos and the rest of the team that developed and tested that CHCP method). That helps a lot - I feel much better about capturing the active code page now.
I've updated the first post in this thread to version 1.8 with the recommended change.
I've edited the first post in this thread to version 1.7. I adopted andresp's idea of using code page (CP) 65001 (UTF-8) to support file names that contain characters that are not in your active code page. However, the feature has not been adequately tested in my mind, so I only activate CP 65001 if...
The very first post of this thread always has the most recent version (currently v1.6). That version should work as long as all characters in filenames are supported by your active code page. I did not incorporate andresp's suggested changes to support all unicode charcters in file names As for the ...
Much better, though that should give you two lines of output since 0.27.0 appears twice in your source. If you want only one then you need to figure out rules for how to choose which one you want. Also, your pattern might give the wrong result if the source includes something like the following: 123...
Currently there is no option to use a different week definition - only ISO 8601 is supported. I considered trying to support additional standards, but opted not to do so. The math should not be too hard, but establishing a sensible/workable set of options and display syntax just became a bit overwhe...
findstr "^" "%FDMEE_BIN%%ERR_FILE%" >nul || del "%FDMEE_BIN%%ERR_FILE%"
for %%F in ("%FDMEE_BIN%%ERR_FILE%") do if %%~zF == 0 del "%FDMEE_BIN%%ERR_FILE%"
I don't see how commas within a field value pose any problem or complication. That is only a complication if the field delimiter also happens to be a comma. Skipping the first line is simple via the /EXC option. According to your sample data, the 18th field also is the last field in the record - Tha...
Unfortunately I've not found a means to standardise delays that isn't impacted by the specs of a PC That is actually fairly simple. Treat your game as a movie, consisting of a series of static frames with incremental changes displayed sequentially to simulate motion. You want the frame rate to be c...