Re: RET ain't RET unless you tell RET it is RET

|--==> "JJ" == Jerry James <james(a)xemacs.org&gt; writes: JJ> I think this is a bit of a red herring. I can get RET to behave as RET JJ> by evaluating anything at all in the *scratch* buffer when XEmacs first JJ> starts up. That is, this is sufficient: JJ> (+ 0 1) C-j () C-j Seems to be sufficient. JJ> I'm seeing what Norbert is seeing. It is as though the first RET you JJ> type gets stuck in a pipe somewhere, then the next keypress makes the JJ> RET take effect, as well as processing that next keypress. That's only half the problem, it's also processing that RET as LFD (which runs `eval-print-last-sexp' in scratch). -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - The only _______ you'll ever need. | | Fill in the blank, yes, it's THAT good! | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|