!-- On Mon 9.Sep'13 at 20:33:43 BST, David Champion (d...@bikeshed.us), wrote: > > I confess I haven't dug my way through the entire debate on this, but so > far I've seen argument along lines of: is it a necessary feature? if it > is necessary, is it necessary to be supported in mutt per se, or can it > be done externally? > > I haven't seen any discussion of what use models it would harm to > support this in mutt. Does anyone have an argument against? > > Lacking that, I would say that if someone submits a good patch it should > be considered. To me it's a good enhancement request. > > (I can take the old "features are bloat, one tool for one job" trope for > granted, but I don't find it very compelling in general and especially > not in this case, where almost all the code necessary is already there > in some fashion.) > > -- > David Champion • d...@bikeshed.us I think it would a very attractive feature for mutt users and should be considered by devs to implement this in mutt. I see no reason for it to be handled by an editor given so many people use different editors with mutt. (For what it's worth :-) )
-- James Griffin: jmz at kontrol.kode5.net A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
