I'm curious, why use the perl command instead of just: sed 's/\$/\n/g' filename.txt > fixed.txt What exactly does perl -i -pe do different ? //Sylvester Marius Roets skrev:

On 9/4/06, Rikard Johnels wrote:

...

I have this odd file filled with the remains of a psion-file that was corrupted. It seems fields are delimites with a $ sign. How can i quickly exchange those for a CR/LF combination ?

/me needs desperately to learn shell scripting and or Perl...

perl -i.bk -pe 's/\$/\r\n/g' filename.txt

Should replace all occurences '$' with CR/LF combinations. If you only want the LF (unix style) then drop the '\r'. Your original file will be saved with a .bk extension. If you are confident that it's working and don't want the backup, drop the .bk as in :

perl -i -pe 's/\$/\r\n/g' filename.txt

HTH Marius

On 9/4/06, Marius Roets wrote:

...

I'm curious, why use the perl command instead of just: sed 's/\$/\n/g' filename.txt > fixed.txt

What exactly does perl -i -pe do different ?

Well, nothing at all :). It's just a different way of doing the same thing.

Actually I just thought of one difference. perl -i -pe 's/\$/\r\n/g' *.txt works just great, whilst the sed command would put it all in one file. Of course there are ways around it with a small shell script, I'm sure. Marius

The commands to do that are already on the system, at least on my system. I am not sure what package they came from but would be willing to investigate that is someone asks. /usr/bin/unix2dos /usr/share/doc/packages/unix2dos /usr/share/doc/packages/unix2dos/COPYRIGHT /usr/share/man/man1/unix2dos.1.gz /usr/bin/dos2unix /usr/share/doc/packages/dos2unix /usr/share/doc/packages/dos2unix/COPYRIGHT /usr/share/man/man1/dos2unix.1.gz

Sylvester Lykkehus schreef: (Top posting reversed)

Marius Roets skrev:

...

On 9/4/06, Rikard Johnels wrote:

...

I have this odd file filled with the remains of a psion-file that was corrupted. It seems fields are delimites with a $ sign. How can i quickly exchange those for a CR/LF combination ?

/me needs desperately to learn shell scripting and or Perl...

(snip)

...

perl -i -pe 's/\$/\r\n/g' filename.txt

I'm curious, why use the perl command instead of just: sed 's/\$/\n/g' filename.txt > fixed.txt

What exactly does perl -i -pe do different ?

Nothing. But perl changes the file *in situ* whereas in sed you always need an auxiliary file to dump the output to. Regards, -- Jos van Kan registered Linux user #152704

On Monday 04 September 2006 19:02, Sylvester Lykkehus wrote:

Not completely true I think. For example sed -i 's/\$/\n/g' filename.txt

That only works with some versions of sed. (Recent GNU versions.) If you're on a Solaris machine, for example, sed -i won't work but perl -i will. -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts