GNOME Bugzilla – Bug 243201
vfolder name problems with "&"
Last modified: 2008-07-03 09:29:31 UTC
Adding a vfolder named "Foo/Bar" leads to weirdness: (1) As long as the vfolder editor is up, it appears in the shell as a folder "Foo" containing an item called "Bar". (2) When you close the vfolder editor, it changes to a folder named "Foo" w/o subfolders. When you select it, the screen says that the folder can't contain messages. It also doesn't go away if you try to delete it. (3) If you exit evo and restart, the mysterious "Foo" folder disappears.
Old, old request. However, al prior reports are closed. So... levae this open. 1.4.x. Only if there's time, 1.4
In a related bug, a vfolder named 'Foo & Bar' gets truncated to 'Foo ' after exiting and re-starting evo. But you probably already knew that.
evolution-2.1.3.2.0.200501160930-0.snap.ximian.10.1: "/": a folder named "foo" and a subfolder named "bar" will be set up; the vfolder with its rules is of course "bar", both are fully accessible and the vfolder rule is working. so it seems like "/" is not escaped. "&": as described by troy in his last comment, it gets truncated. :-( "#": no problems, closing bug 236477 dealing with this.
"/" is a duplicate of bug 271105 which should be fixed in 2.1.4 according to changelog.
/ IS legal in the vfolder editor, it can be used to define subfolders, but not to name individual folder paths. Hmm, & seems to be a problem with the stupid libxml api not escaping things we give to it. i.e. this: if (fr->name) { work = xmlNewNode (NULL, "title"); xmlNodeSetContent (work, fr->name); xmlAddChild (node, work); } is apparently wrong, even though GetContent de-escapes everything.
adding vfolders keyword.
also see bug 320582
futuring, sorry
*** Bug 320582 has been marked as a duplicate of this bug. ***
IMHO the ability to create a hierarchy and nested vFolders easily by using a "/" char is an important *feature*, not a bug. I do use it regularly, it keeps my vFolders structured and makes spotting the vFolder I want easy.
Note: With current Evo versions there is absolutely no weirdness whatsoever as described in the original report regarding "/". This just works perfectly and entirely smoothless. It just creates a folder structure. All sub- and parent-folders are fully functional vFolders as well.
Bumping version to a stable release.
*** Bug 500039 has been marked as a duplicate of this bug. ***
Created attachment 113865 [details] [review] proposed evo patch for evolution; As suggested by Not Zed, just escaping the title works fine. But I've such a feeling we will need to escape all text values in saving, just to be sure it will work properly. (I didn't change the behaviour for the slash, because I agree with guenther, it's fine to create subfolders based on the name.)
Changing summary from "vfolder name problems with "/" and "&"" to "vfolder name problems with "&"".
Milan looks fine to me. Commit
Committed to trunk. Committed revision 35716.