From owner-freebsd-current  Wed Jun 26 07:25:54 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA11228
          for current-outgoing; Wed, 26 Jun 1996 07:25:54 -0700 (PDT)
Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA11211
          for <current@freebsd.org>; Wed, 26 Jun 1996 07:25:42 -0700 (PDT)
Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id QAA29111 for current@freebsd.org; Wed, 26 Jun 1996 16:25:31 +0200
Message-Id: <199606261425.QAA29111@ra.dkuug.dk>
Subject: RFC: cut&paste funtionality...
To: current@freebsd.org (FreeBSD current)
Date: Wed, 26 Jun 1996 16:25:31 +0200 (MET DST)
From: sos@freebsd.org
Reply-to: sos@freebsd.org
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


So, I'm left with a little problem about how to handle the marked
text when new output goes to the screen, possibly messing up
the marked area or moving it around. There is 3 possible
solutions to this:

1.	Catch all updates and change the marking to comply

2.	Remove the marking on all updates.

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

Now, 1 above is almost impossible, so unless we will accept
a MAJOR slowdown on screen updates, this is not really an
option. 2 above is possible (thats the route I've started)
but it generates quite alot of code. 3 is easy and does
not cost anything...

So comments are VERY welcome...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt             (sos@FreeBSD.org)             FreeBSD Core Team
               So much code to hack -- so little time.