Re: define-key acting strange..

[Andreas Schwab <schwab@suse.de>]

"D. Goel" <deego@glue.umd.edu> writes:

|> ( A quick update before i go away for the long
|> weekend.. to... Maryland!!!.. )..
|> 
|> 
|> All of the problem was being caused by the one line in that
|> expression:  (guess i will have to wait another day to learn GDB :)
|> 
|> 
|>  (define-key [t] <foo>).. and that <foo> could be anything ..

*Note (elisp)Format of Keymaps::.

`(t . BINDING)'
     This specifies a "default key binding"; any event not bound by
     other elements of the keymap is given BINDING as its binding.
     Default bindings allow a keymap to bind all possible event types
     without having to enumerate all of them.  A keymap that has a
     default binding completely masks any lower-precedence keymap.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."