Subject: pico ctrl-j/ctrl-u

From: Bob Walker <[email-masked]>
Date: Fri, 19 Mar 1993 10:06:53 +0000 (GMT)

This may be a FAQ, but we've recently found a problem with 'pico'.

If you do 'CTRL-J' to justify a paragraph and then move the cursor
elsewhere in the document and do 'ctrl-u' (inadvertantly, I guess), it
copies the unjustified text previously justified to that point in the
document.

This is little more than a nuisance to those of us who know about
computing, but as we at Bristol are about to unleash 'pico' as our default
editor in 'elm' (sorry..we're unable to move to 'pine'!) we'd like to know
if anyone can see a fix?

Bob Walker

---

From: Terry Gray <[email-masked]>
Date: Fri, 19 Mar 1993 07:30:25 -0800 (PST)

Bob,
I think it is fixable.

We want Ctl-U to be able to "undo" a justification, and the kill buffer is used
for this, but it should be possible to note that the kill buffer currently
contains the input to a justification, and clear it when the cursor is moved. 

I'll check with Mike and get it on the enhancement list.

-teg

---

From: Dan Schlitt <[email-masked]>
Date: Fri, 19 Mar 1993 12:26:38 -0500 (EST)

Careful now.  If I move the cursor back to its original position doesn't
the principle of least suprise say that I ought to be able to undo the ^J?
So when do you clear the kill buffer?  Don't you have to maintain a lot of
state to know when to do the clear?

/dan

Dan Schlitt                           School of Engineering Computer Systems
[email-masked]        City College of New York
(212)650-6760                         New York, NY 10031

---

From: Michael Seibel <[email-masked]>
Date: Fri, 19 Mar 1993 10:54:16 -0800 (PST)

The kill buffer really shouldn't have been used for this.  It's even more
apparent with the mark/cut functionality of the next version as the buffer
should see increased use as a place to park text that's being shuffled
around. 

The ideal solution would be a general, consistent "undo" command (you
mentioned state?).  It's on the list, but is hard to say whether or not
it'll make it into the next release... 

-mikes