Hi,

I am using mutt as follows:

andrew@ilium~$ mutt -v
Mutt 1.5.17 (2007-11-01)
Copyright (C) 1996-2007 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 2.6.21.5-smp (i686)
ncurses: ncurses 5.6.20070217 (compiled with 5.6)
libidn: 0.6.10 (compiled with 0.6.10)

and have just one niggling problem: I am unable to scroll _up_ in a
message withing Mutt by using the backspace key. This key appears to
be bound:

<BackSpace> previous-line          scroll up one line

but when I use it the error message is:

Key is not bound.  Press '?' for help.

which shows the keybinding for Backspace :-) It puzzles me more than
a little as all other keys: Enter, Page up, page down, end etc all
function fine.

Any thoughts?

Andrew

--
Now I can praise him, now that I can stand by to mourn
and speak before this web that killed my father; yet
I grieve for the thing done, the death, and all our race.
I have won; but my victory is soiled, and has no pride.

[ Post a follow-up to this message ]

On 2007-11-17, andrew <andrew@ilium.invalid> wrote:
> Hi,
>
>  I am using mutt as follows:

[config snipped]

> and have just one niggling problem: I am unable to scroll _up_ in a
> message withing Mutt by using the backspace key.

Same symptoms here with:

Mutt 1.5.15 (2007-04-06)
System: Darwin 8.11.1 (i386)
ncurses: ncurses 5.6.20061217 (compiled with 5.6)

I haven't looked into it myself but I would definitely appreciate
a fix for this issue.

Ian

--
Ian Gregory
http://www.zenatode.org.uk/ian/

[ Post a follow-up to this message ]

* Ian Gregory on Saturday, November 17, 2007:
> On 2007-11-17, andrew <andrew@ilium.invalid> wrote: 
>
> [config snipped]
> 
>
> Same symptoms here with:
>
> Mutt 1.5.15 (2007-04-06)
> System: Darwin 8.11.1 (i386)
> ncurses: ncurses 5.6.20061217 (compiled with 5.6)
>
> I haven't looked into it myself but I would definitely appreciate
> a fix for this issue.

For me this happened when I used a $TERM with kbs=^H (eg. xterm
or xterm-256color etc.). I did:

$ infocmp > xterm-256color.src

changed kbs=^H to kbs=\177, then

$ tic -x xterm-256color.src

HTH

c
--
Python Mutt utilities <http://www.blacktrash.org/hg/muttils/>

[ Post a follow-up to this message ]

On 2007-11-17, Christian Ebert <blacktrash@gmx.net> wrote:
> * Ian Gregory on Saturday, November 17, 2007: 

[...]
[vbcol=seagreen] 

[...]
[vbcol=seagreen]
> For me this happened when I used a $TERM with kbs=^H (eg. xterm
> or xterm-256color etc.). I did:
> $ infocmp > xterm-256color.src
> changed kbs=^H to kbs=\177, then
> $ tic -x xterm-256color.src

Thanks for that Christian it has completely resolved the problem,
although I have _absolutely_ no understanding of the fix :-) Do you
think this is worthwhile posting as a _mutt_ bug (flea)?

Thanks again for the fix!!

Andrew

--
Now I can praise him, now that I can stand by to mourn
and speak before this web that killed my father; yet
I grieve for the thing done, the death, and all our race.
I have won; but my victory is soiled, and has no pride.

[ Post a follow-up to this message ]

* andrew on Sunday, November 18, 2007:
> On 2007-11-17, Christian Ebert <blacktrash@gmx.net> wrote: 
>
> [...]
> 
>
> [...]
> 
>
> Thanks for that Christian it has completely resolved the problem,
> although I have _absolutely_ no understanding of the fix :-) Do you
> think this is worthwhile posting as a _mutt_ bug (flea)?

I don't believe this would be considered a mutt bug. Probably
this was already on mutt-dev, I'm too lazy to look it up ATM. Eg.
if you use Terminal.app with the correct (not default) $TERM
setting nsterm (and it's derivatives), it works.

The other possibility to make it work, if you use mutt only in 1
TERM environment is to enter the following in your muttrc:

bind index,pager ^? previous-page

where "^?" is entered as Ctrl-V Ctrl-<BackSpace> (at least in
Vim).

c
--
Python Mutt utilities <http://www.blacktrash.org/hg/muttils/>

[ Post a follow-up to this message ]

On 2007-11-17, Christian Ebert <blacktrash@gmx.net> wrote:

> For me this happened when I used a $TERM with kbs=^H (eg. xterm
> or xterm-256color etc.). I did:
>
> $ infocmp > xterm-256color.src
>
> changed kbs=^H to kbs=\177, then
>
> $ tic -x xterm-256color.src

Thanks, That worked for me. I am using TERM=screen (Mac OS X) to
fix a problem I had with slrn where it would not display threads
nicely. I had noticed that it displayed threads fine when using
screen so while in screen I dumped the "TERMCAP" entry and saved
it in ~/.termcap. Then in my .profile I do:

TERM=screen
TERMCAP=$(cat .termcap)

But slrn uses slang, whereas mutt uses ncurses. So I just followed
your advice an now I have a ~/.terminfo/s/screen entry with the
modified backspace character.

I find all this terminal stuff to be one of the most confusing things
about Unix. Since very few people use real hardware terminals any
more I have often wondered why there can't be a single standard
"virtual" terminal that everybody uses.

Ian

--
Ian Gregory
http://www.zenatode.org.uk/ian/

[ Post a follow-up to this message ]