Ways to aware that some string contains a substrings

[berserker]

This is as robust as simple batch gets:

Code: Select all

@echo off
set "string1=needleb"
set "string2=aneedle"
set "string3=aneedleb"

if /i "|||%string1%"=="|||needle%string1:needle=%" echo needle is at the beginning
if /i "%string2%|||"=="%string2:needle=%needle|||" echo needle is at the end
if /i not "%string3%"=="%string3:needle=%" echo string contains needle
pause

needle is at the beginning
needle is at the end
string contains needle

nice solution. actually also depend on TS whether he needs to trim off spaces(or unseen characters in front or end) or not.

[siberia-man]

The foxidrive suggestion is almost the best. But it doesn't work in some specific cases when NEEDLE contains "=" or "*" symbols (in addition to the existing troubles with few specific symbols). Read my first post =)

[berserker]

The foxidrive suggestion is almost the best. But it doesn't work in some specific cases when NEEDLE contains "=" or "*" symbols (in addition to the existing troubles with few specific symbols). Read my first post =)

so why don't you show more on your specific cases. help us to help you. surely you can't expect others to guess what's happening right?

[foxidrive]

There is no foolproof method that is simple.

If you want foolproof and simple then it's time to turn to VBS at the very least

[siberia-man]

so why don't you show more on your specific cases. help us to help you. surely you can't expect others to guess what's happening right?

have you ever read the points I have mentioned early? I began from the description of existing solutions and shown possible issues.

If you want foolproof and simple then it's time to turn to VBS at the very least

Yes. VBS is good replacement, even though I prefer writing on JS, PERL, or migrate to CYGWIN shell.

[Squashman]

PERL, or migrate to CYGWIN shell.

But then your script doesn't become very portable if others need to use it.

[berserker]

PERL, or migrate to CYGWIN shell.

But then your script doesn't become very portable if others need to use it.

actually writing all these languages SHOULD be "portable", as long as there is the appropriate interpreters and the environment etc.

[Squashman]

PERL, or migrate to CYGWIN shell.

But then your script doesn't become very portable if others need to use it.

actually writing all these languages SHOULD be "portable", as long as there is the appropriate interpreters and the environment etc.

Should I quote some of your previous posts about you saying things about being smart and you know what I mean. I think you know what I mean by portable. People who use PERL and CYGWIN know they need certain things installed. Someone who comes along and sees a script written in some other scripting language other than batch on this website may try to run the script as a batch file not realizing they need something else installed to run it. That is why I like to see people post disclaimers about how their scripts need to be run if they are not native to Windows. You were originally posting all kinds of solutions when you first joined here but were not explaining that you needed perl or grep or sed or awk installed.

[siberia-man]

But then your script doesn't become very portable if others need to use it.

yes or not - depends on tasks. The proper organization of a code could minimize influence of environment. Moreover, we could hide all differences into configuration files.

[berserker]

Should I quote some of your previous posts about you saying things about being smart and you know what I mean. I think you know what I mean by portable.

well then obviously we have different wave length. I am also sure you know I am not talking about that kind of "portable". Shall we stop at that, agree to disagree?