中国DOS联盟

Originally posted by 26933062 at 2008-5-29 09:35 PM:

Hehe, the person above really has an efficiency issue.

I also considered the efficiency issue.

Just thought of another question: Doesn't the system spend time when processing!str:~0,1! for variable truncation?

Combined with everyone's discussion, variable truncation may be more efficient than findstr.

I think Brother WANKOILZ's should still be improved.
if "!str:~0,1!"=="" echo.

Last edited by zqz0012005 on 2008-5-29 at 09:56 PM ]

Hehe, I just want to target the simple form of text by the original poster, and the method is not perfect. Piping + findstr will reduce efficiency. Of course, if you want to be comprehensive, you can only use findstr.

What I have isn't simple text; it's just modifying INF files. First, help me take a look at the problem on floor 15.

Determine if there is a

@echo off&setlocal enabledelayedexpansion
for /f "tokens=*" %%a in (a.txt) do (
set "str=%%a"
set "str=!str:

@echo off&setlocal enabledelayedexpansion

for /f "delims=" %%i in (1.txt) do (

echo %%i|findstr "^\$">nul&&echo.

for %%j in (%%i) do set str=!str! %%j

echo !str:~1!&set str=

)

pause>nul

Remove the spaces in front of the lines at the same time:

@echo off&setlocal enabledelayedexpansion

for /f "delims=" %%i in (1.txt) do (

echo %%i|findstr "^\$">nul&&echo.

for %%j in (%%i) do set str=!str! %%j

echo !str:~1!&set str=

)

pause>nul

The symbols need to be escaped with \ if used as ordinary symbols in findstr. Brothers 26 and zq ignored this, and I also discovered it after testing the previous code.

Last edited by WANKOILZ on 2008-5-29 at 10:27 PM ]

The code on floor 19 can remove the spaces in front of the lines...
echo %%i|findstr "^\$">nul This method is very inefficient.

Originally posted by WANKOILZ at 2008-5-29 10:16 PM:
Remove the spaces in front of the lines at the same time:

@echo off&setlocal enabledelayedexpansion

for /f "delims=" %%i in (1.txt) do (

echo %%i|findstr "^\$">nul&&echo.

fo ... 




This is a test...


cc dd will delete cc together

Reply to the upstairs: It has been improved, but it's not as easy to use as 26933062's. tokens=* ensures that the spaces before the line are removed and the subsequent data remains unchanged, which should be the best method. As for the format like findstr "^\$">nul, I'm using it for the first time, but the format like "^$" doesn't work.

Forgot that "" are special characters in findstr

tokens=* removes leading spaces, Xiao Lou can always be innovative, really cost-effective!

Last edited by zqz0012005 on 2008-5-29 at 10:32 PM ]

@echo off

for /f "delims=:" %%a in ('findstr /n ".*\" a.txt') do set .%%a=a

for /f "tokens=1* delims=:" %%a in ('findstr /n .* a.txt') do (

   if defined .%%a echo.

   for /f "tokens=*" %%i in ("%%b") do echo.%%i

)

pause

Methods to completely match

@echo off

for /f "delims=:" %%a in ('findstr /n ".*\" a.txt') do set .%%a=a

for /f "tokens=1* delims=:" %%a in ('findstr /n .* a.txt') do (

   if defined .%%a echo.

   for /f "tokens=*" %%i in ("%%b") do echo.%%i

)

pause

The method upstairs is really unique.
But I don't understand ".*\":
1. Why isn't ".*" added later, such as: .*\.*
2. What does the two dots mean in "..*".
Please explain it for me upstairs.

There is also a problem...

Can we delete the lines starting with ; which are comments without deleting the ; in the middle of characters?

; asdasdasd
asd;asd
; qweqewqwe
---------------------------
asd;asd

* represents 0 or n repetitions of the preceding character.
. represents at least one character.
If it is ".\*\", then it also matches the result of like this. That is: the content between is not matched.

* means 0 or n repetitions of the preceding character
. means at least one character.
If it is ".*\", then it will also match results like . That is: with no content inside also matches.

It is very clear, thank you.
Also, please help again: Why not add .* at the end, in the form of ".*\.*", what is the difference between this and not adding it?

Reply to post 27: The code in post 25 meets your requirements

Last edited by WANKOILZ on 2008-5-29 at 10:59 PM ]

If you add .* later, then lines like add which do not end with ] will also be matched, and such lines are not what the original poster wants.