Re: problem with backspace key in xterm-256color
- To: mutt-users@xxxxxxxx
- Subject: Re: problem with backspace key in xterm-256color
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Sun, 15 Jun 2008 17:31:29 -0500
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=default; bh=oCOb4WMC7N3Sx6f6eyyH6O00DPw=; b=h/0G uGuaK7DRstfNcEanceug1rJsjb0O4fII5nZMUpAx5oGqrpyyiKSo9WF5O+gziI8q a4eF1Ny05jEbdhM3UObWRGIE8Hx+p1M9YXkmWDS8ctDHPo3PmVm6sbB6zNrqBCjC fx4sYuiI0AicOM0vLW4WJEAv695HIH0mCvV0Ad8=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=lUNQ7Ya+dECM0XGgI7nafSaE3nkEd+ZvY8625RZ3YdkDy+uPqAF30G1QyQCQOWqcuHCKzmd8oCeyINrWetcLUnRdFz7MIpWVVNDdD3xxaqQVKATR+sJQ3oSgpeCsKIJjAzZcGNPpR9P/gvHRFZWuAf4cOMMb6TS+4p0sw0MelO0=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20080615221606.GA7492@xxxxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20080615211139.GA5197@xxxxxxxxxxxxxxx> <20080615215518.GA66971@xxxxxxxxxxxxx> <20080615221606.GA7492@xxxxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.18 (2008-06-02)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday, June 15 at 06:16 PM, quoth Marianne Promberger:
> That helped my solve the problem by using "\177" instead of
> <backspace> in the .muttrc
Heh, sure, that's one way to do it.
> both with TERM=xterm and TERM=xterm-256color, pressing Ctrl-v
> backspace shows up as:
>
> ^?
Okay... (that's the same as \177)
>> If not, is your termcap perhaps different? Try these two commands:
>>
>> infocmp -1 -L xterm | grep key_backspace
>
> key_backspace=\177,
>
>> infocmp -1 -L xterm-256color | grep key_backspace
>
> key_backspace=^H,
HUH! Interesting. You have a broken xterm termcap file. Where did it
come from?
> That is good enough for me, as I'm lazy and I'd rather not recompile
> mutt with slang :)
As long as it works for you, that's the important thing.
> But it occurred to me that another way to solve this would be if
> mutt skipped checking for my terminal's color support.
Can't. That's part of the ncurses library. Essentially, there is no
"standard" way of saying "I want to draw this letter in color 157", so
it *has* to look up how to say that. The act of looking it up is what
tells it how many colors the terminal supports.
> If mutt could skip checking for TERM=xterm-256color, that would make
> my life easier anyway, since with that TERM some remote shells
> refuse to operate, because they say "I know nothing about your
> terminal" (I've worked around that problem by setting practically
> all my ssh .bashrc aliases to start with "export TERM=xterm && ssh
> ... ".
My solution was to copy an nsterm-16color termcap file (that's what
terminal I use) to all those remote servers. :) That way I can tell
myself it's not a workaround, it's the "correct" way of providing
information about my terminal.
~Kyle
- --
For every complex problem, there is a solution that is simple, neat,
and wrong.
-- H. L. Mencken
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkhVmEEACgkQBkIOoMqOI14BMACg+q+K0uS5HvSCZvAz+9xUv74Y
TvcAnjFJLKOEBDX4Kutaip1t/7Nr9aCE
=59bb
-----END PGP SIGNATURE-----