On Thu, Oct 26, 2000 at 10:20:44PM +0200, Juergen Salk wrote:
> * Thomas Dickey <[EMAIL PROTECTED]> [001026 18:42]:
> > On Wed, Oct 25, 2000 at 10:55:26PM -0400, kiss the sun and walk on air wrote:
> > > how do i get my numeric keypad working in mutt? i'm using helix gnome
> > > on a debian woody system, running mutt from inside the gnome
> > > terminal. if I have numlock on i get numbers at the bash prompt, but
> > > not inside of mutt. (mainly to use it for quicker entry of message #'s
> >
> > that's because the X modifiers don't predefine numlock, so unless the
> > emulator makes a special check for it, it's not properly supported.
> > I added checks in XFree86 xterm last year, and that works reasonably
> > well (breaks of course if one tinkers with xmodmap or the key translations).
>
> Let me pick this up for a related issue that seems to be a 'never ending
> story'. I am using mutt in conjunction with gnome-terminal, because of
> it's build-in URL support. (I really can't get used to
> urlview, which this tears the URLs out of the written context
> of the messages.)
>
> However, I could not manage to make the Pos1- and Home-keys working
which is Pos1?
> within mutt running in a gnome-terminal. This problem seems to be
> related to mutt, because Pos1 and Home both work e.g. in tin and vim
> running in a gnome-terminal but not in mutt.
hmm (I'm not at the moment on a system where I can test gnome-terminal).
tin and vim may not be using quite the same environment as mutt: tin uses
either termcap or terminfo (usually ncurses), and this is what I noted
about it for ncurses:
# this describes the alpha-version of Gnome terminal shipped with Redhat 6.0
gnome|Gnome terminal,
bce,
kdch1=\177, kf1=\EOP, kf2=\EOQ, kf3=\EOR, kf4=\EOS,
use=xterm-color,
and I don't see khome listed in the corresponding infocmp output (which I
expect is an omission on my part). What $TERM and infocmp do you have?
It's possible that your mutt is linked with slang, which may not put the
terminal into application mode, so some of the function keys will map
incorrectly (at least going by the terminfo entry alone). vim also uses
some internal tables to fill in the termcap/terminfo. So it's hard to
say unless we know what the terminal description _is_, and then see how
it is used.
--
Thomas E. Dickey <[EMAIL PROTECTED]>
http://dickey.his.com
ftp://dickey.his.com
