> With all respect, the feature you suggest (as point 2.) might be useful to
some people, even though I don't know precicely for what.
Actually, now, I *can* see at least one feature for which saving the original
subject in a separate header field could be of use. But that feature should be
implemented as an extension, that may *optionally* be enabled/applied *after*
direct editing the subject (e.g. for one of the reasons mentioned in comment
#31). If, after enabling this feature for an message, any follow-up messages
received with that same original subject *automagically* would be substituted by
the new subject, then that would be really useful.
But, the above suggested feature *should not* be considered if it in any way
delays the implementation of direct editing the subject line; e.g. as described
in comment #31.
I do willingly admit that I haven't analysed and considered any side-effects
that this might have. It was just an idea that happened to cross my mind.
(In reply to my own comment #30)
> With all respect, the feature you suggest (as point 2.) might be useful to
some people, even though I don't know precicely for what.
Actually, now, I *can* see at least one feature for which saving the original
subject in a separate header field could be of use. But that feature should be
implemented as an extension, that may *optionally* be enabled/applied *after*
direct editing the subject (e.g. for one of the reasons mentioned in comment
#31). If, after enabling this feature for an message, any follow-up messages
received with that same original subject *automagically* would be substituted by
the new subject, then that would be really useful.
But, the above suggested feature *should not* be considered if it in any way
delays the implementation of direct editing the subject line; e.g. as described
in comment #31.
I do willingly admit that I haven't analysed and considered any side-effects
that this might have. It was just an idea that happened to cross my mind.