In
[EMAIL PROTECTED],
on 09/06/2006
at 12:13 AM, Alan Altmark [EMAIL PROTECTED] said:
VM allows the sysprog to set the line editing defaults. The most
reasonable are: CHARDEL OFF LINEND # ESCAPE LINEDEL OFF.
Is there any reaon not to use Field Mark for LINEND?
--
Shmuel (Seymour
In [EMAIL PROTECTED], on 09/06/2006
at 01:22 AM, Paul Gilmartin [EMAIL PROTECTED] said:
Why? How?
Command stacking. I assume that was what Alan had in mind as well.
People today are quite accustomed to graphic workstations where no
displayable character is usurped for editing functions.
In a recent note, Shmuel Metz (Seymour J.) said:
Date: Thu, 7 Sep 2006 11:18:35 -0300
Is there any reaon not to use Field Mark for LINEND?
I'd love to. Depending on terminal emulator, keyboard, and map.
I tried to do the same for ISPF, but it wouldn't let me. Apparently
ISPF has
On Thursday, 09/07/2006 at 11:18 ZW3, Shmuel Metz (Seymour J.)
[EMAIL PROTECTED] wrote:
VM allows the sysprog to set the line editing defaults. The most
reasonable are: CHARDEL OFF LINEND # ESCAPE LINEDEL OFF.
Is there any reaon not to use Field Mark for LINEND?
Because my fingers refuse
In a recent note, Alan Altmark said:
Date: Wed, 6 Sep 2006 00:13:24 -0400
- Line editing ought to be disabled by default on graphic
terminals.
For for full-screen applications, yes: not for line-mode input.
By coincidence, the userid and password fields on the VM logo are
On Wednesday, 09/06/2006 at 01:22 CST, Paul Gilmartin
[EMAIL PROTECTED] wrote:
essentially a full-screen app. But if you press enter and go back
into
line mode, then the default VM line editing characters (those
specified or
defaulted in SYSTEM CONFIG) are in effect, even before you log
Alan Altmark wrote:
once the CRT came into being and we all learned to use it, CHARDEL and
LINEDEL went the way of the dodo Maybe the next time we think about
re-versioning z/VM we'll consider changing those two to OFF.
But they didn't vanish quietly. The console task maintained
In [EMAIL PROTECTED], on 09/04/2006
at 08:53 AM, Paul Gilmartin [EMAIL PROTECTED] said:
Perhaps autoskip should operate in the reverse direction,
I'm not sure that is the best solution, but the problem is certainly a
nuisance.
o Of late, companies are requiring ever more complex passwords,
On Tuesday, 09/05/2006 at 10:11 ZW3, Shmuel Metz (Seymour J.)
[EMAIL PROTECTED] wrote:
o Of late, companies are requiring ever more complex passwords, with
mixed-case, numerics, and special characters. VM line editing
usurps several special characters; to enter them literally, they
Edward
There is (still I guess) an aspect of the VM logon panel, copied in the
NetView logon panel[1], which, to my mind indicated a lack of understanding
of human factors in the implementation of the 3270 data stream and its
effect on the operator experience.
When deciding whether or not to use
In a recent note, Chris Mason said:
Date: Mon, 4 Sep 2006 11:50:21 +0200
If the input data is guaranteed to fill the field, then the use of the
autoskip bit is appropriate. Ideally such a field will be part of a
sequence of such fields so that reaching for the tab key will not be
Chris Mason wrote:
If the input data is guaranteed to fill the field, then the use of the
autoskip bit is appropriate. Ideally such a field will be part of a
sequence of such fields so that reaching for the tab key will not be
necessary within the whole sequence.
I agree with the above.
My
12 matches
Mail list logo
