After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 581462 - "Undo" functionality for deleting memos
"Undo" functionality for deleting memos
Status: RESOLVED DUPLICATE of bug 442603
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-05-05 12:52 UTC by phil.labram
Modified: 2012-06-16 20:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description phil.labram 2009-05-05 12:52:40 UTC 
A memo accidentally deleted can not be restored.

I was viewing information in a memo (where I can not edit it). I highlighted some text and pressed ctrl + X. This deleted the whole memo. I could not then find a way to restore the memo, despite paste being available.

Can functionality change to either indicate that the whole memo is about to be delete or add a simple way to restore the memo.

Thanks



Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc)
BugBuddy Version: 2.22.0
Comment 1 Akhil Laddha 2009-05-06 03:47:40 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 413618 ***
Comment 2 phil.labram 2009-05-06 08:17:01 UTC 
Bug 413618 refers to the contents of the memo, while I was referring to the memo itself. If you delete a memo using the delete option you are given a warning that all will be lost and not recoverable. However using ctrl+X you are given no such warning and all is lost.
Comment 3 Akhil Laddha 2009-05-06 09:21:44 UTC 
oh..okay
Comment 4 Akhil Laddha 2011-03-01 09:13:59 UTC 
duplicate of bug 442603 ?
Comment 5 André Klapper 2012-06-16 20:58:39 UTC 

*** This bug has been marked as a duplicate of bug 442603 ***