X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sun, 11 Apr 2010 11:33:05 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.3: Backspace key not working in GNU screen.
Message-ID: <20100411093305.GN28908@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <u2v49e721a81004081305q61e00044hba10b82e6900aa3d AT mail DOT gmail DOT com>  <q2q49e721a81004081307q2db70190p176cd745b2a78388 AT mail DOT gmail DOT com>  <m2n416096c61004100231je0fea482s7a9a7d2e82cd2792 AT mail DOT gmail DOT com>  <20100410140811 DOT GA8593 AT ednor DOT casa DOT cgf DOT cx>  <p2k416096c61004100900j2d3b3567gdd068feb17547ec3 AT mail DOT gmail DOT com>  <20100410161626 DOT GA1904 AT ednor DOT casa DOT cgf DOT cx>  <20100410173607 DOT GA3986 AT ednor DOT casa DOT cgf DOT cx>  <20100410181700 DOT GA7321 AT ednor DOT casa DOT cgf DOT cx>  <i2t416096c61004101409ka5c18517obfc3a09e284a0e98 AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <i2t416096c61004101409ka5c18517obfc3a09e284a0e98@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Apr 10 22:09, Andy Koppe wrote:
> Christopher Faylor wrote:
> > I'm not 100% sure that this is the right fix but the new snapshot at
> > least works around the problem.
> 
> Thanks.
> 
> > The problem is that screen explicitly sets VERASE to 0.  I believe that
> > it does that to mean "there is really no erase character since I'm
> > handling that".
> 
> You're right. Zero is the value of the _POSIX_VDISABLE constant for
> disabling special characters. Therefore, using c_cc[VERASE] as the
> backspace keycode was a bad idea all along. Sorry for suggesting it in
> the first place.
> 
> > That should not cause Cygwin to send a null character.
> > I think it should probably just send the default \177 character.
> 
> Makes sense given the botched design, but of course it does mean that
> the user's backspace keycode setting is ignored. Also, 'screen' would
> be expecting what was set in c_cc[VERASE] as the backspace keycode.

That would be surprising.  If you set VEARSE to 0 on Linux, a following
tcgetattr returns 0 as the VERASE value.  stty prints "<undef>".  The
same holds true for other settings like VKILL, VINTR, etc.  So, if the
process sets VERASE to 0, and is then puzzled to get a 0 VERASE value
from the OS, it's the application's fault.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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