This is another case for mutt-ot, MFT+RT set, works only for subscribers, hope to see you there.
=- Alain Bench wrote on Tue 5.Jun'07 at 15:50:45 +0200 -= > [changing defaults] > For this and other debates: Don't waste time and energy fighting > against stability in itself. Stability is a good thing. Stability > *is* part of the equation. Better try to overcome stability with > more intense improvements. ... "more intense" ... Besides that in the current case I agreed to recommend to keep the "tradition" to reserve "," rather than "§" for macro examples (for practical general use, not just a special case), generally this doesn't affect the view on defaults or changes, in this case the desire not to bind "," by default for a new function that's about to come. (note: I don't want to have an extra function and with it a default binding at all, so "," wouldn't be overridden anyway ;). But if it had to be, then I wouldn't treat "," special to keep it empty/ reserved without such a note to inform the user -- not dev -- why) Your point is to keep the new function away from ',' so _oldies_ could keep by their already installed example macros running via ',' not overwriting a default binding for the new function, so that they could learn or use it instantly/ directly when they already know about it and have everything setup (required! not usable by default). How often do you expect such _oldies_ to look at '?' at all to look out for keybindings they've been using for years and memorized well to even have a chance to notice the new function by accident? Oldies are either too used to their setup not to change it or look at '?', or if they are aware of the change (by announcement), then they're smart enough to notice it as new function in '?', even if unbound by default, to (re-)bind it as they like. Newbies stumbling over the function by rtfm or in '?' help can't use it without background setup requiring to read about it, where an example to bind the new function to a desired key (whatever key you want to suggest as default) can be copied&pasted. I understand your concern for the existing users: convenience to instantly use the feature, no changes with macro treatment either. But if you had to choose/ decide between the 2 (oldies convenience not to change habits and gain convenience vs. newbies convenience to have a smoother entry), which path would you go? You're sacrificing simplicity of learning for stability or instant direct use for a relatively small oldies group, neglecting the possibilty that generally always a new stability could be reached once a new default matures to "established". You're mistaken that I don't value stability, au contraire. I just value corrections of bad decisions even more! :) Bad habit doesn't make things better. It's all about improving, not just for oneself (and fellow oldies), but the newcomers, too, isn't it? -- © Rado S. -- You must provide YOUR effort for your goal! EVERY effort counts: at least to show your attitude. You're responsible for ALL you do: you get what you give.
