HP3000-L Archives

February 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Woods <[log in to unmask]>
Reply To:
Jeff Woods <[log in to unmask]>
Date:
Tue, 22 Feb 2000 18:06:28 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
At 05:15 PM 2/22/00 , Stan Sieler wrote:
> > > >  Good.  I approve.  Now, fix the @#$%^ paste design flaw and I'll
> try using
> > > >  it again!

> > "It's not a bug, it's a feature."
>
>The problem I referred to is the paste of a "partial line" copy (or cut).

[snip]

>Now, I don't particularly care how many people in New Mexico think it should
>work the way it does now in QCTERM.  They're all wrong.

[snip]

>If it *doesn't* work right, it should at least work in a manner that
>minimizes mistakes.  Unconditionally appending a <return> leads to mistakes.

[snip]

>How often do you paste a partial-line copy (or cut)?
>
>...of those times, how often do you want a <return> at the end of the paste?

Well...  I'm in New Mexico (and both the enchiladas and the company I had
on my last trip to Las Cruces were excellent! :) but I agree with Stan on
this one.  :)  Partial line paste should *not* imply a <return>.  And there
should be a way to copy a whole line *without* the <return> (although it
would also be nice to be able to optionally pick up the return
somehow).  It works under Xterm on the fvwm2 window manager I find myself
using lately.  Seems like it should be a snap for a cool product and smart
bunch of folks I know just an afternoon drive down I-25 from here.  ;)
--
Jeff Woods
[log in to unmask] (preferred)
[log in to unmask] (deprecated)

ATOM RSS1 RSS2