Re: [Evolution] Long standing feature request (Undo operation)


It may be 15 years old, but it's only got 31 comments on it and
a massive gap of 5 years 2010-2015 with only 10 comments in the last
years. So, TBH, there doesn't really seem to be a massive clamouring
for it.

Perhaps not, but there are also 6 subsequently filed bugs that were
closed as duplicates, and probably many more people who just don't know
that bug reports can be used to request features in addition to
reporting things that are broken.

Yes, it might be a useful thing and I might use it once or twice a
year, but I can see that to do it properly it would have to be built
into every operation and that is a massive task and something that
affects the whole of the gui codebase I presume - possibly even the
other backend components (if, in between deleting and undoing,
client expunges, then that needs to be handled and involves the

I don't think it's as easy as some of the bug comments seem to think.

That's disappointing, but understandable. Do you think the difficulty
of implementing this is unique to Evolution's design, or is it just the
way things are in general? I only ask because of the prevalence of this
feature in other email clients I've used.


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]