From: Juan C. A. B. <jc...@ro...> - 2000-09-22 23:52:13
|
I seem to be having problems with sed, too. I can't get it to match forward slashes (as in pathnames) in the regular expressions. For example: sed -e 's%newronin/%%g' applied to a file that contains: --- c:/newronin/file.cpp --- will leave that line intact. I'm using the sed program that comes with the MinGW supplement toolset. It says "GNU sed version 2.05". Salutaciones, JCAB --------------------------------------------------------------------- Juan Carlos "JCAB" Arevalo Baeza | http://www.roningames.com Senior Technology programmer | mailto:jc...@ro... Ronin Entertainment | ICQ: 10913692 (my opinions are only mine) JCAB's Rumblings: http://www.metro.net/jcab/Rumblings/html/index.html |
From: Greg C. <chi...@mi...> - 2000-09-23 01:07:07
|
Juan Carlos Arevalo Baeza wrote: > > I seem to be having problems with sed, too. I can't get it to match > forward slashes (as in pathnames) in the regular expressions. For example: > > sed -e 's%newronin/%%g' > > applied to a file that contains: > > --- > c:/newronin/file.cpp > --- > > will leave that line intact. I'm using the sed program that comes with > the MinGW supplement toolset. It says "GNU sed version 2.05". I think '%' might be magical. Maybe it looks for an environment variable; I just don't know. This works for me: <testfile sed -e 's.newronin/..' and returns c:/file.cpp for the file you gave above. I'm using sed-3.02 . You can probably get it from one of the links below, although I haven't tested them. The URL also has some good pointers to sed tutorials if you're interested. http://sunsite.org.uk/public/usenet/news.answers/comp.editors/sed_FAQ,_version_014 GNU sed v3.02 32-bit binaries and source, using DJGPP compiler. Requires 80386 SX or better. Also requires 3 CWS*.EXE extenders if run under MS-DOS. See section 5.5 ("What is CSDPMI*B.ZIP and why do I need it?"), below. This version will run under Windows or under MS-DOS. The binary archive (sed302b.zip) contains 2 executables, sed.exe and gsed.exe. sed.exe was compiled with the DJGPP regex library, which is POSIX.2-compliant and usually runs faster; gsed.exe was compiled with the GNU regex library, which though it runs slower and is almost POSIX.2-compliant, it has a richer set of regexs and will run faster on certain complex regexs which cause the DJGPP sed.exe to run extremely slowly. ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/sed302b.zip ftp://ftp.cdrom.com/.27/simtelnet/gnu/djgpp/v2gnu/sed302b.zip ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/sed302s.zip ftp://ftp.cdrom.com/.27/simtelnet/gnu/djgpp/v2gnu/sed302s.zip |
From: Juan C. A. B. <jc...@ro...> - 2000-09-27 00:07:13
|
At 04:56 PM 9/22/2000 -0700, I wrote: > I seem to be having problems with sed, too. I can't get it to match > forward slashes (as in pathnames) in the regular expressions. For example: > >sed -e 's%newronin/%%g' OK... This is getting to my nerves. Help, please? I'm using sed 3.02 now, from Cygwin. Still not working. I have a file that contains a line like this: --- d:/progra~1/micros~3/vc98/include/winbase.h --- I want to make a sed script that weeds lines like this out. In fact, I want to weed out lines that contain the "d:/progra~1/micros~3/vc98" path, but that's another story. I run the following sed script: sed -e '\%/vc98%d' It doesn't weed out the line. If I do instead: sed -e '\%.vc98%d' It removes the line without problems. So far, so good (if you can call it good). Now, if I try this: sed -e '\%3.vc98%d' It again doesn't remove the line either. The problem is not with the % character. I tried others. Does anyone have any insights as to why this could be happening? Salutaciones, JCAB --------------------------------------------------------------------- Juan Carlos "JCAB" Arevalo Baeza | http://www.roningames.com Senior Technology programmer | mailto:jc...@ro... Ronin Entertainment | ICQ: 10913692 (my opinions are only mine) JCAB's Rumblings: http://www.metro.net/jcab/Rumblings/html/index.html |