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 574278 - Automatic link updates can wreak havoc
Automatic link updates can wreak havoc
Status: RESOLVED DUPLICATE of bug 350990
Product: tomboy
Classification: Applications
Component: General
0.13.x
Other All
: Normal minor
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-05 14:54 UTC by Chris
Modified: 2009-03-05 15:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Chris 2009-03-05 14:54:14 UTC
Say I create a note and give it a title, perhaps mistakenly, that is a very common word.  Recently I created one called "test".  Once I do that, Tomboy goes out into all my other notes and links every occurrence of the word "test" to this new note.  This is great, and how I think tomboy should operate.  What I don't like is if I now change the name of this note to something else, say "Bug Test", Tomboy goes out and replaces every occurrence of the word "test" with "Bug Test" thereby changing the textual content of my notes.  "Bug Test" does not make sense in a note I've written about grading a "test".  If I delete the note "Bug Test", Tomboy does not revert all of the new occurrences of "Bug Test" back to "test", it leaves them as greyed out "Bug Test".  I realize this is part of the foundation of Tomboy, but you can see how it can create lots of problems.  

I propose that the first part is correct, always link all occurrences of the name of a note to the note, but do not allow changing the note name to change all of the occurrences of the note name. 

I think that changing the name of a note should disassociate that note with all of the old links and return them to normal text. It should then associate all occurrences of the new name.  

Other information:
Comment 1 Sandy Armstrong 2009-03-05 15:29:18 UTC
The title's a little misleading, but we're talking about this problem in bug #350990.  Marking as dupe, and copying your comment over.

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