Re: Key mapping issues with Putty and 4GL
Posted in 2008
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL
You can also try stty erase <ctrl-V> <backspace key> <enter> Ctrl-V tells many terminals that they should not process the next character as an action (if it already corresponds to one) but should instead take it literally. If the backspace key is already being interpreted as some action, you will need the ctrl-V in order to get the backspace key to be sent as an argument to stty erase rather than be converted to whatever (wrong) action it is currently mapped to. -- Kevin Cherkauer Software Engineer IBM Informix Dynamic Server -- Database Kernel "Ian Michael Gumby" <im_gumby@hotmail.com> wrote in message news:910d15d7-5988-47a8-9477-10437cc2cd74@k30g2000hse.googlegroups.com... > try stty erase (then hit the backspace key)
Just to be pedantic: Many versions of stty will recognize the sequence of a caret ("^") followed by a letter and some of the special characters to indicate the keyboard character that is normally generated by holding the Control key down and pressing the second character of the sequence. Check your friendly man page. Walt. > -----Original Message----- > From: informix-list-bounces@iiug.org [mailto:informix-list- > bounces@iiug.org] On Behalf Of Kevin Cherkauer > Sent: Friday, July 11, 2008 4:18 PM > To: informix-list@iiug.org > Subject: Re: Key mapping issues with Putty and 4GL > > You can also try > > stty erase <ctrl-V> <backspace key> <enter> > > Ctrl-V tells many terminals that they should not process the next > character > as an action (if it already corresponds to one) but should instead take > it > literally. If the backspace key is already being interpreted as some > action, > you will need the ctrl-V in order to get the backspace key to be sent > as an > argument to stty erase rather than be converted to whatever (wrong) > action > it is currently mapped to. > > -- > Kevin Cherkauer > Software Engineer > IBM Informix Dynamic Server -- Database Kernel > > > "Ian Michael Gumby" <im_gumby@hotmail.com> wrote in message > news:910d15d7-5988-47a8-9477- > 10437cc2cd74@k30g2000hse.googlegroups.com... > > > try stty erase (then hit the backspace key) > > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments).
I am pretty sure stty is off base. The keys work as expected in bash,
stty -a has erase = ^H, Cntl V <backspace> prints ^H, my termcap enter
has :kb=^H: . The issue is only in 4gl and dbaccess. The backspace
goes left, but is none destructive in these programs.
On Jul 11, 3:34 pm, "Hultgren, Walt" <walt.hultg...@emory.edu> wrote:
> Just to be pedantic: Many versions of stty will recognize the sequence of a caret ("^") followed by a letter and some of the special characters to indicate the keyboard character that is normally generated by holding the Control key down and pressing the second character of the sequence. Check your friendly man page.
>
> Walt.
>
Sorry, should have paid a bit more attention. What I should have said is that I've never seen 4GL have anything but a nondestructive backspace when in a mode that involves character-addressable screen control such as during forms input or after statements such as CLEAR SCREEN.
For example try the following program:
main
define x char(10)
prompt "Enter: " for x
display "|", x, "|"
prompt "Return to continue... " for x
clear screen
prompt "Enter: " for x
display "|", x, "|"
end main
On my version of 4GL (c4gl 7.2x, Solaris), the first prompt occurs when the program is in "line" mode. At that point, backspaces are destructive. The second prompt just lets you view the display statement output.
Once the screen has been cleared, input to a prompt statement identical to the first now has a nondestructive backspace. At that point I think 4GL has gone into raw mode input or something similar.
The only thing that I know of that will push 4GL back into line mode is the RUN statement or maybe starting a report to a pipe.
If you do find a way to do what you want, please post it.
Walt.
> -----Original Message-----
> From: informix-list-bounces@iiug.org [mailto:informix-list-
> bounces@iiug.org] On Behalf Of JaxenT
> Sent: Friday, July 11, 2008 5:37 PM
> To: informix-list@iiug.org
> Subject: Re: Key mapping issues with Putty and 4GL
>
> I am pretty sure stty is off base. The keys work as expected in bash,
> stty -a has erase = ^H, Cntl V <backspace> prints ^H, my termcap enter
> has :kb=^H: . The issue is only in 4gl and dbaccess. The backspace
> goes left, but is none destructive in these programs.
>
>
> On Jul 11, 3:34 pm, "Hultgren, Walt" <walt.hultg...@emory.edu> wrote:
> > Just to be pedantic: Many versions of stty will recognize the
> sequence of a caret ("^") followed by a letter and some of the special
> characters to indicate the keyboard character that is normally
> generated by holding the Control key down and pressing the second
> character of the sequence. Check your friendly man page.
> >
> > Walt.
> >
>
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.
If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).