中国DOS联盟

sed ":nt; $!{N; s/\n//; tnt}; s/。/&\n\n/g" myfile.txt

According to the idea of change, then sed can be improved like this

sed ":nt; $!{N; s/\n//; tnt}; s/。/&\n\n/g" myfile.txt

Originally posted by lxmxn at 2008-7-15 15:05:
According to the idea of change, then sed can be improved like this

sed ":nt; $!{N; s/\n//; tnt}; s/。/&\n\n/g" myfile.txt

It is possible, but if the file is too large, it won't work, right? Can the pattern space hold too much content?

Originally posted by 26933062 at 2008-7-15 15:29:

It is possible, but if the file is too large, it won't work, right? Can the pattern space hold too much content?

Hmm, if the file is large, it probably won't work.

Just tried it. Files under 10K are processed relatively quickly, but above 50K, it's relatively slow, and files over a megabyte are not suitable.

Reply to floor 45

This is my execution result. Except for changing the test file path, nothing else has changed. The line "cd.>d\c.txt" is not necessary.

Batch files (Batch File, referred to as BAT files) are a kind of most commonly used executable files under DOS. It has flexible operability and can adapt to various complex computer operations. The so-called batch processing means automatically executing several specified DOS commands or programs in a specified order.
That is, it is to collect the originally executed commands one by one and execute them in batches, and the program file can be ported to other computers for operation, so it can greatly save the tediousness of repeatedly entering commands. At the same time, batch files also have some programming characteristics. It can flexibly control the execution of the program through extended parameters, so it is very practical in daily work. Batch. bat. cmd. Each has its own strengths and weaknesses.

Originally posted by qzwqzw at 2008-7-16 08:20:
Reply to post 45
This is my execution result
Except for changing the test file path
Nothing else has changed
The sentence "cd.>d\c.txt" is not necessary

Finally figured it out, it turns out that there can't be that slash after n..
change f:\111\d\a.txt /nf:\111\d\c.txt /from "nnn" /to " yyy " /in not "。"

Brother qzwqzw, can you have a slash there?

It seems that you lack sufficient understanding of relative paths and absolute paths. The \ prefix refers to the root of the current drive. Obviously, because your data file is not on the current drive, it causes an error.

Yes, I've always been a bit hazy about relative paths... So that's how it is!

BEGIN {RS="。"}
{
gsub (/\n/,"")
print $0"。"}

Actually, awk is very convenient for handling such problems. It's just that many people have preconceived ideas.

BEGIN {RS="。"}
{
gsub (/\n/,"")
print $0"。"}

As usual, I only use code

I don't know if change supports wildcards