Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site pur-phy.UUCP Path: utzoo!linus!philabs!seismo!harpo!gummo!whuxlb!floyd!vax135!ariel!houti!hogpc!houxm!ihnp4!ixn5c!inuxc!pur-ee!CSvax:Pucc-H:pur-phy!crl From: crl@CSvax:Pucc-H:pur-phy.UUCP Newsgroups: net.emacs Subject: Question about regular expression searches Message-ID: <852@pur-phy.UUCP> Date: Fri, 29-Jul-83 12:35:10 EDT Article-I.D.: pur-phy.852 Posted: Fri Jul 29 12:35:10 1983 Date-Received: Wed, 3-Aug-83 23:33:47 EDT Organization: Purdue Univ. Physics Dept., W. Lafayette, IN Lines: 17 I have run into a possible bug in regular expression searches. Perhaps it isn't really a bug, but just a feature of the way it works. If I say (re-search-forward "^") and repeat this a number of times, I would expect to successively find the beginning of the next number of lines. However, what happens is that I find the first beginning of line, and not move from there. Is this supposed to be the correct behavior? I sometimes would like to use (re-query-replace-string "^" "/* ") for example to sometimes comment out some C code. However, if I don't change an occurrence, I'm stuck there. I am therefore forced to use (re-query-replace-string "^." "/* &") which has the (sometimes) unfortunate side-effect of not finding a blank line. Looking into the source, most of the regular expression code in advance() behaves like this for the characters like '^', '$', etc. Comments? Charles LaBrec pur-ee!Physics:crl purdue!Physics:crl