From owner-freebsd-current  Wed Jun 26 12:34:11 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA00212
          for current-outgoing; Wed, 26 Jun 1996 12:34:11 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA00200;
          Wed, 26 Jun 1996 12:34:08 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id MAA26096; Wed, 26 Jun 1996 12:33:43 -0700 (PDT)
To: sos@freebsd.org
cc: current@freebsd.org (FreeBSD current)
Subject: Re: RFC: cut&paste funtionality... 
In-reply-to: Your message of "Wed, 26 Jun 1996 16:25:31 +0200."
             <199606261425.QAA29111@ra.dkuug.dk> 
Date: Wed, 26 Jun 1996 12:33:43 -0700
Message-ID: <26094.835817623@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 1.	Catch all updates and change the marking to comply

Probably not worth it.

> 2.	Remove the marking on all updates.

This is how I've seen other systems do it, and it's reasonably
acceptable from a UI standpoint.

> 3.	Only show the marked text when actually doing the
> 	cut action, remove as soon as the mousebutton is 
> 	released.

I don't like this one and the systems I've seen which did it this way
were very annoying to use. :)

					Jordan