Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!pequod.cso.uiuc.edu!dorner
From: dorner@pequod.cso.uiuc.edu (Steve Dorner)
Newsgroups: comp.sys.next
Subject: Re: Edit
Message-ID: <1991Jan16.194811.27849@ux1.cso.uiuc.edu>
Date: 16 Jan 91 19:48:11 GMT
References: <1991Jan16.124936.28168@santra.uucp>
Sender: news@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at U-C
Lines: 28

In article <1991Jan16.124936.28168@santra.uucp> jmunkki@hila.hut.fi (Juri Munkki) writes:
>appears that WriteNow supports some nice keyboard commands for editing
>(go to end of line, go to beginning of line and selection changes too),
>but Edit doesn't support any of them.
>Is there a real reason for this inconsistency?

I suspect the reason is that WriteNow was a product before the Cube; it
is a port (or a rewrite) of a program that already had the features.  NeXT
hasn't gotten around to it for Edit (whether they intend to is a separate
question, of course).

>Then there's the Find/grep function of Edit. I tried a simple regular
>expression replace command, but it appears that it doesn't support stuff
>like \(.*\)$ replaced with \1foobar, which just appends foobar to the
>end of every line.

There's my biggest complaint.  I'd gotten very used to saying:

cmd-a shift-cmd-l sed 's/whatever/something/'

to get around the problem.

Then they took shift-cmd-l away.  I could do without the automatic
parens matching (manual was fine); I really, really want REAL regular
expressions.
--
Steve Dorner, U of Illinois Computing Services Office
Internet: s-dorner@uiuc.edu  UUCP: uunet!uiucuxc!uiuc.edu!s-dorner