On Monday, 03 September 2007 at 08:44, Rocco Rutte wrote: > Hi, > > * Marco d'Itri [07-09-01 11:58:56 +0200] wrote: >> On Aug 31, Thomas Roessler <roessler@xxxxxxxxxxxxxxxxxx> wrote: > >>> Sounds like a good idea. I wonder, though, whether it might be >>> useful to move the subwindow toward the bottom of the screen, to >>> basically grow out of the status bar / entry line. I'd suspect that >>> most long-time mutt users will have their focus down there when they >>> start dealing with any interaction that they expect will involve a >>> choice. >> Yes! > >> I believe that a window in the middle of the screen really looks out of >> place. Dynamically widening the status bar would be much more elegant >> and consistent with the mutt UI. I strongly agree with this too. In hindsight, the emacs technique of growing the input line as necessary seems like the obvious way to go. > The problem is that it's really hard to get it implemented with translators > in mind. Given some structured input to mutt_multi_choice(), how do you > decide which characters can be ommitted per locale and which can't? > > E.g. the sorting choice now contains 'frm' for 'from' or 'sender'. You can't > assume that for all languages it makes sense to remove vowels, not to speak > of lanuages with non-latin letters. I don't follow this argument. If the input line grows to fit the input, what needs to be abbreviated?
Attachment:
pgpWYzENXgpEv.pgp
Description: PGP signature