From owner-freebsd-hackers  Tue Jan 17 04:52:29 1995
Return-Path: hackers-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id EAA06913 for hackers-outgoing; Tue, 17 Jan 1995 04:52:29 -0800
Received: from wcarchive.cdrom.com (wcarchive.cdrom.com [192.216.191.11]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id EAA06907 for <freebsd-hackers@freefall.cdrom.com>; Tue, 17 Jan 1995 04:52:28 -0800
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by wcarchive.cdrom.com (8.6.8/8.6.6) with SMTP id EAA01503 for <freebsd-hackers@wcarchive.cdrom.com>; Tue, 17 Jan 1995 04:52:21 -0800
Received: by dg-rtp.dg.com (5.4R2.01/dg-rtp-v02)
	id AA27288; Tue, 17 Jan 1995 07:51:48 -0500
Received: (rivers@localhost) by ponds.UUCP (8.6.9/8.6.5) id UAA19381; Mon, 16 Jan 1995 20:53:32 -0500
Date: Mon, 16 Jan 1995 20:53:32 -0500
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199501170153.UAA19381@ponds.UUCP>
To: freebsd-bugs@wcarchive.cdrom.com, freebsd-hackers@wcarchive.cdrom.com
Subject: Probable bug in /bin/sh (backslash processing again.)
Sender: hackers-owner@FreeBSD.org
Precedence: bulk


I just tried to post from my FreeBSD 2.0R machine, using the inews shell
script supplied with my ancient version of cnews.

Apparently, the newer "sed" acts differently than the older one, which
causes inews to not find any newsgroups from /usr/lib/news/active.

The offending line in inews looks like:

egreppat="^(` sed -e 's/[.+*()|[]/\\\\&/g' -e 's/,/|/g' <$nglist `) "

If you set nglist to /tmp/t1, and have a single line in /tmp/t1 which
looks like this (no leading space):

  rec.collecting


And then execute the following:

egreppat="^(` sed -e 's/[.+*()|[]/\\\\&/g' -e 's/,/|/g' </tmp/t1 `) "
echo $egreppat

The answer you get is:

^(rec&collecting)

Instead of the expected:

^(rec\.collecting)

(I've verified that to be the correct result on an HP/UX machine, and
 a Sun4 with SunOS 4.1.x)

This is most likely a bug in /bin/sh backslash processing within quotes.

I had tried my hand at fixing the last set of these - but didn't get
very far when someone else had already fixed them.   Unfortunately, I
don't know who that someone was to report this additional problem.

	  - Thanks -
	- Dave Rivers -