On Wed, 16 Mar 2011 10:23:07 +0100, Luca Capello <l...@pca.it> wrote: > > Thanks for reporting. This is a change in behavior that should have been > > documented, true. and sorry for that. > > > > I will submit a patch that adapts the default config file to point out > > that only one ui interface is valid. To make our life easier we won't > > support dynamic plugins and fallback plugins. > Is this the only rationale to remove such a feature?
The rationale is that the previous UI names were an abdomination and something had to be changed about them :-). Or do you remember off hand if it is called TTYUI.TTY or TTY.TTYUI? (and it was case-sensitive too, 'TTYUI', but 'Blinkenlights') So the current behavior is that we have changed the ui names to just drop everything before the dot and become cases insensitive. So you can now invoke it with: -u basic or -u blinkenlights etc. The old names will still work for backwards compatability. But when working on that code, we decided that we would not want to increased complexity in dynamically detecting UI modules and fallback if one fails. > > We are even considering to deprecate the Curses interface :-). > Please do not. AFAIK Curses.Blinkenlights is the only interface that > allow "interactive" commands: even if they are not documented, at least > 'q' nicely quits OfflineIMAP. So does CTRL-C in all other backends now :-). I see your point, though we are just very short on manpower. And I mean *very* short (basically, me at the moment). So keeping 5 UI backends up to date is more than the current devs are willing to do. In addition the curses ui is a pain when it comes to exceptions, it will freak out the output of your console. The traceback will be blanked out by curses so you can't even see what has gone wrong etc. Nothing that is unfixable, but also nothing that current devs are interested in working on. > > So this is more of a documentation bug than everything else. > No, it breaks existing configurations, thus it is also a regression. It is indeed. It also warns you what has gone wrong and how to fix it. Should we provide an automatic upgrade path? Perhaps, but I don't want to have offlineimap fudge with a user's config. Not an excuse, but: I did not do that incompatability on purpose. When I coded up the new ui config, I was not even aware that it is possible to hand it multiple uis. But the damage has been done and released, so the only thing I *could* do is to pick the first ui if a list is given and use that one. offlineimap has been on hiatus since essentially 2006 and all of the devs have changed, so this is some of the transition pain as new devs becomes familiar with the code. Thanks for using offlineimap and looking forward to your curses patches :). Sebastian
pgpd1j656cfxD.pgp
Description: PGP signature
