DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=TdWh8G2LnlWl8c8r
	JzaraWyyNTewxS+Sv0QYvUyDkjGZblvwGk/vJQ+Mg4oeKhxggh1wDieQsgtmhjb+
	eiiAho7VtNNwCetQbdb69TTl7P6IL8rV80SxXR9/wuoHkTCtRiMFS9vzZh1AZNFj
	vI4C3R3v2G1V2oCOOF/dp9Wz3fk=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Running texconfig breaks backspace in Bash/MinTTY
To: cygwin@cygwin.com
References: <20160316114546.GO29016@dinwoodie.org>
From: Ken Brown <kbrown@cornell.edu>
Message-ID: <56E952E5.2000205@cornell.edu>
Date: Wed, 16 Mar 2016 08:34:45 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160316114546.GO29016@dinwoodie.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 3/16/2016 7:45 AM, Adam Dinwoodie wrote:
> Here's an interesting bug: normally in a Bash session in MinTTY,
> backspace and Ctrl+H both delete the previous character, as expected.
> However, after running texconfig and returning to the shell, both the
> backspace key and Ctrl+H appear to just print "^H" to the terminal.
>
> It looks like this is genuinely the terminal trying to render a
> backspace character, rather than just backspacing, given the following:
>
>      $ printf ^H | xxd
>      00000000: 08                                       .
>
> (To get that, I typed "printf {backspace} | xxd".)
>
> It's not clear to me whether this is Bash, MinTTY or texconfig that's
> misbehaving.  Ctrl+W to delete a word, Ctrl+R to get (for me) fzf's
> history search, and using the up and down arrows to navigate history all
> work.  Running Vim, opening a new Bash shell from within the duff one,
> or SSHing to another box has Ctrl+H working just fine within that
> process, but the bugged behaviour resumes when I return to the original
> Bash shell.

I can't reproduce this on my system.  I tried 'texconfig --help' and 
'texconfig conf'.  What's the precise texconfig command that you used?

Could this have something to do with fzf?

Ken


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