<<< Date Index >>>     <<< Thread Index >>>

mutt/1649: Re: mutt/1649: mutt/1649: interactive :set mbox_type=<Tab> completion



The following reply was made to PR mutt/1649; it has been noted by GNATS.

From: Will Yardley <mutt-dev@xxxxxxxxxxxxxxxxx>
To: bug-any@xxxxxxxxxxxxx
Cc: Mutt Developers <mutt-dev@xxxxxxxx>
Subject: Re: mutt/1649: mutt/1649: interactive :set mbox_type=<Tab> completion
Date: Tue, 2 Aug 2005 21:14:37 -0700

 On Wed, Aug 03, 2005 at 06:05:01AM +0200, Brendan Cully wrote:
 
 >  > Hrm - this doesn't quite work as I'd expect....
 
 >  > Hitting tab repeatedly doesn't seem to switch to the next type, and
 >  > hitting "set mbox_type=m<tab> doesn't return a list of possible
 >  > completions.
   
 >  To be honest, it's not what I was expecting either. I usually use
 >  set ?mbox_type<return>
 >  to get that information, and don't see the point in having two ways of
 >  doing it. But I'm just imitating what mutt was doing for every other
 >  variable.
   
 Right - that's how I've done it - I never even noticed that you could do
 it this other way. But I guess that makes sense if it's the way
 everything else works.
 
 >  I agree that tab-completion/cycling would be nice. I guess you could
 >  submit it as a change-request.
 
 Yeah - I guess the trick here would be to make the behavior (relatively)
 consistent, which might be hard.
 
 w