HP3000-L Archives

February 1997, Week 2

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:
Roy Brown <[log in to unmask]>
Reply To:
Roy Brown <[log in to unmask]>
Date:
Fri, 7 Feb 1997 13:57:38 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (60 lines)
In article <0015100005110754000004*@MHS>, Paul Christensen
<[log in to unmask]> writes
> Before you ask for return=enter,

Nope. I asked for 'Return = Enter in Block Mode' (i.e. it toggles on and
off with Block Mode).

'Return = Enter' is already available on HP terminals and on terminal
emulators such as Reflection, as a configuration option, and it can be
toggled with an escape sequence.

>stop and think about how visual mode works in QEDIT.
>Pressing carriage return, does just that, bounces me down the page, one
>line.  Press enter, means transmit my changes back to the computer.

Nope. Carriage Return means 'fly back to the start of the line'. It's
Line Feed that means 'move down one'. So you are saying that when you do
a CR in QEDIT, QEDIT does a CR/LF. It's what you want of course, but it
shows that QEDIT is second-guessing you.

Now for QEDIT to be responding to the CR, it can't be in Block Mode.
(Software can perfectly well respond to 'Enter' in character mode if it
is expecting it as a possibility, but not vice versa).

So my request wouldn't apply here, and wouldn't affect your usage of
visual mode in QEDIT.

(I don't actually have QEDIT, so here is a gap for a possible
contradiction from Robelle.......:-)

> The "real" problem is with the keyboard manufacturers for PC's,
>they should correctly identify the carriage return, as return, and
>the enter key then means enter. (I know, fat chance of that)...
>
Sorry, you've lost me here. When you press a key on a PC keyboard, it
sends a scan code to the hardware, which passes it on to your OS and
your application. The OS makes what it will of the scan code, and your
app makes what it will of the mapped ASCII the OS passes along.

I agree that it's a good idea that when I press 'e' I get 'e' and not
'o', but in the last analysis it's just a mapping. Those of us in the UK
who have accidentally let DOS default their keyboard to US mappings, and
found all the squiggly things come up different (<,@#.~}] etc) will know
what I mean.

A PC is not like a terminal, which uses Return/Enter to decide whether
or not to transmit back to the host. It's just 'hey, this guy pressed a
key. It was 0Ah' (or whatever). Then the app (Reflection or whatever)
says 'OK, what do I do when I get that keystroke?'

Either way, the action is several levels remote from whichever piece of
plastic your typing finger pushed to complete a circuit....


--
Roy Brown               Phone : (01684) 291710     Fax : (01684) 291712
Affirm Ltd              Email : [log in to unmask]
The Great Barn, Mill St 'Have nothing on your systems that you do not
TEWKESBURY GL20 5SB (UK) know to be useful, or believe to be beautiful.'

ATOM RSS1 RSS2