From: "Al G." <qor072@gmail.com>
To: cygwin@cygwin.com
Subject: Re: 1.7.3: Backspace key not working in GNU screen.
Date: Mon, 12 Apr 2010 12:37:00 -0000 [thread overview]
Message-ID: <l2h49e721a81004120536vfe233cci625dee5d2b5ff624@mail.gmail.com> (raw)
>> It sounds as though no change is required in screen for this.
>
>Correct.
>
>> screen is an ancient program from the dim mists of early terminal days, so I'm
>> not surprised that it has some problems of this kind.
>
>Don't worry, screen isn't doing anything wrong here. Setting the
>VERASE key on the console device to _POSIX_VDISABLED (i.e., zero) is
>perfectly legitimate, it's the console using that as the backspace
>keycode that caused the problem.
@ Larry: Sorry, still not used to responding to the digests. I PEBCAKd
the Spam info.
Where should I look to see this patch once it's released?
-Al
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2010-04-12 12:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 12:37 Al G. [this message]
2010-04-12 13:28 ` Larry Hall (Cygwin)
-- strict thread matches above, loose matches on Subject: below --
2010-04-09 16:30 Al G.
2010-04-09 19:16 ` Larry Hall (Cygwin)
[not found] <u2v49e721a81004081305q61e00044hba10b82e6900aa3d@mail.gmail.com>
2010-04-08 20:08 ` Al G.
2010-04-08 20:41 ` Larry Hall (Cygwin)
2010-04-10 9:31 ` Andy Koppe
2010-04-10 14:08 ` Christopher Faylor
2010-04-10 16:00 ` Andy Koppe
2010-04-10 16:16 ` Christopher Faylor
2010-04-10 17:36 ` Christopher Faylor
2010-04-10 18:17 ` Christopher Faylor
2010-04-10 21:09 ` Andy Koppe
2010-04-11 2:11 ` Christopher Faylor
2010-04-11 9:33 ` Corinna Vinschen
2010-04-11 12:28 ` Corinna Vinschen
2010-04-11 14:39 ` Andrew Schulman
2010-04-11 14:50 ` Andy Koppe
2010-04-11 14:47 ` Andy Koppe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=l2h49e721a81004120536vfe233cci625dee5d2b5ff624@mail.gmail.com \
--to=qor072@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).