DosTips.com

I could have sworn that I tested it :roll: Fixed. A minor update is that it now uses a US as delimiter. It's nowhere used anymore. However, we meet its original semantics if we take it for this purpose. Perhaps this is something that jeb feels more comfortable with. The downside is that the macro in...

I was referring more to why MS didn't implement it when they refactored Batch with the release of NT. There's no hope of something like that happening again in the future, as they've gone in a new direction with PowerShell (almost two decades ago already). https://github.com/microsoft/terminal/blob/...

I have a feeling my demonstration that measured length is not a good basis for making assumptions about displayed width has left you in paralysis :lol: In this case - don't worry, you just know now that the two are not connected. However, it will still work for printable ASCII, box drawing and block...

our general default test string Huh? Did we really define that? :lol: However, I actually still have something like that in my test case. :: make sure we are in the spotlight: @if "%~1"=="" start /realtime conhost "%~f0" 1&exit /b @echo off &setlocal DisableDelayedExpansion :: 33 set "str0=&<>|^-+*...

I absolutely get your point, jeb. And if you would've asked me a decade ago, my answer was pretty much the same as yours. However, it's a fact that we can't meet the expectation of a user who only relies on what the macro name suggests. Not only because we are technically unable to do that. Also bec...

pieh-ejdsch What if we claim (or define) that control characters are not part of a string? Would that be reasonable? :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :initStrLen :: Computes the number of resulting UTF-16 code units in a string. :: %strLen% str [len] :...

This is now unbelievably fast. Kudos! However, I admit that I immediately changed the code to get rid of the variables i and o, as they seemed like code obfuscation :lol: Talking of obfuscation - is there any good reason to prefer ... for /f tokens^=15delims^=^ %%3 ... ... to the more readable ... f...

Hmm, the new code performs slightly worse in my tests. Expanding !%%1:~4095,1! twice might be the reason, although it's a clever way to handle a space at this position.

I'm still trying to address other given feedback without performance impact. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :initStrLen :: Computes the number of resulting UTF-16 code units in a string. :: %strLen% str [len] :: str - [ByRef In] Name of the variable ...

This is so impressive

BTW Was this known to work? This would have been my expectation:

So, we define that delayed expansion is enabled but the cmd may gives us the finger
Like if I go to a hardware store to buy an 8mm nut, but the shop assistant decides that I only get one if I can show the matching screw
Got it. Thanks!

Yes, of course, I fully understand why it works ... not 🤪🥴
I get why you use !=! since this can't ever be a defined variable. However what puzzles me is why it even makes any difference if it comes before the caret (or after it, as this seems to work too).
Anyway, I just accept it

Steffen

I would never have thought of that
FWIW You could also update this in your previous codes. When you're logged in, you'll see an edit button (pencil) at the top of each of your posts. (Although it doesn't matter if not. The content of the strLen macro is not affected, only its initialization.)

Your HEX magic is incredible :lol: Also for short strings it's now only negligibly slower. The performance gain for longer string is remarkable though. That's how I'm going to save it into my tool collection: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :initStrLe...

but I assumed there were no quotes for the variable That's a fair assumption. We can just remark it in the macro description as this is our contract with the user :wink: I hadn't noticed the reduction with "FOR %%H IN (FEDCBA9876543210)" Everything that comes before the "set StrLen=..." will not be...