Subject: | |
From: | |
Reply To: | |
Date: | Wed, 23 Feb 2000 10:24:02 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Re:
> One of the things that has always annoyed me about Reflection is its lack of
> support for ctrl-c/ctrl-v; though other than that, its copy/cut and paste
> behavior is consistent with other applications. Please do not add yet
Reflection is, first and foremost, a terminal emulator.
It darn well *has* to transmit that control-C / control-V to the
host computer. You'd be more than a little annoyed if you were
trying to interrupt an HP-UX process with control-C if Reflection
simply copied the current selection into the paste buffer!
Thus, Reflection had to implement a non-transmitting key solution.
Now, that said, I applaud QCTerm's solution ... one that I lobbied for ...
with QCTerm, you can say "I want control-C/control-V to be treated like
ordinary characters...transmit them to the host computer and don't
treat them special". With that, I can use QZModify/VEModify in QEDIT
to do upcase (control-C) and split (control-V). I can send "interrupt"
to HP-UX processes (control-C). But...and this is important...at my
choice, I can change the setting and, voila! control-C / control-V
are now copy/paste ... which I would do if I'm doing heavy
editing of text. This is the way the world should be: configurable.
SS
Stan Sieler [log in to unmask]
www.allegro.com/sieler/wanted/index.html www.allegro.com/sieler
|
|
|