[gentoo-user] Re: Unusual console input problem certain keys dead

2009-01-14 Thread Harry Putnam
Willie Wong  writes:

> As to how I know C-v is verbatim? That came from trying to create
> ASCII art by hand ... :)

He he... yeah thats the way thinking works... bouncing around like
that.

I've used C-v for years as a way to see what is actually being sent
from the keyboard.. I never knew it meant `verbatim' but in fact that
is how I've used it... to show verbatim what is sent...
Thanks again.




Re: [gentoo-user] Re: Unusual console input problem certain keys dead

2009-01-14 Thread Willie Wong
On Wed, Jan 14, 2009 at 05:11:17PM -0600, Harry Putnam wrote:
> I'm curious how'd you know it was readline related? 

Since it also appears in SSH, it is something wrong with the box, and
not how you interface with it. 

You said "Ctrl-v fixed it", so odds are that you are not in the wrong
keyboard layout. One of the few things that I happen to remember about
C-v is that for readline it means "verbatim", so I took a wild, flying
guess. 

As to how I know C-v is verbatim? That came from trying to create
ASCII art by hand ... :)

Best, 

W
-- 
Willie W. Wong  ww...@math.princeton.edu
408 Fine Hall,  Department of Mathematics,  Princeton University,  Princeton
A mathematician's reputation rests on the number of bad proofs he has given.



[gentoo-user] Re: Unusual console input problem certain keys dead

2009-01-14 Thread Harry Putnam
Willie Wong  writes:

> On Wed, Jan 14, 2009 at 03:59:17PM -0600, Penguin Lover Harry Putnam
> squawked:

>> Key `e' and `/' when pressed just do nothing whatever.  I think
>> there way be a bell since I see a flash when ssh'd in from and
>> Xterm in a X session on another machine.  I may not have sound
>> enabled... not sure right now.

[...]

> Sounds to me like a problem with readline. Is your /etc/inputrc or
> ~/.inputrc per chance corrupted? 
>
> You can try re-installing readline and/or baselayout (baselayout
> is responsible for /etc/inputrc). 

I think you're on to something... moving ~/.inputrc  and /etc/inputrc to 
...inputrcX  Stopped the problem.

Then I put /etc/inputrc back and left ~/.inputrcX renamed.

That also works... examining .inputrcX, I had a multi-line entry
involving back slashing quite a few double quotes in the
entry... (A lengthy rsync command with a number of command line
exclusions). 

Apparently some error there with the newlines or back slashing
double quotes.

I couldn't really identify the error but deleting the entry has made
the problem go away... thanks... good call.

I'm curious how'd you know it was readline related?