Summary | _getSpecialUse() does not set sort_delimiter |
Queue | IMP |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | |
Requester | thomas.jarosch (at) intra2net (dot) com |
Created | 08/13/2013 (4340 days ago) |
Due | |
Updated | 09/18/2013 (4304 days ago) |
Assigned | |
Resolved | 09/18/2013 (4304 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
personal namespace, they will all share a delimiter so there should
be no reason to have to manually define one.
sort order even in the same namespace. As the default delimiter is
'.' and my server uses '/', that would mess it up.
be sorted correctly:
Foo
Foo/bar
Foo/bar/baz
Foo2
since '/' > any character/number in sorting.
It's not needed here because we can guarantee that all mailboxes will
contain the same delimiter (since we don't allow special mailboxes to
live outside the personal namespace).
personal namespace, they will all share a delimiter so there should
be no reason to have to manually define one.
sort order even in the same namespace. As the default delimiter is '.'
and my server uses '/', that would mess it up.
Though I manually changed the default delimiter to '/' in the
Imap_Client source code to test the effects and the result still
looked ok to me.
I tried to look at Imap_Client/test/Horde/Imap/Client/SortTest.php but
couldn't find an obvious example/test for the hierarchical sort.
Can you give a short example how this is intended to be used?
Perhaps we can work out a more verbose 'sort_delimiter' phpdoc text
that explains what it is actually doing.
personal namespace, they will all share a delimiter so there should be
no reason to have to manually define one.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ _getSpecialUse() does not set sort_delimiter
Type ⇒ Bug
State ⇒ Unconfirmed
as mentioned on the dev mailinglist,
imp/lib/Prefs/Special/SpecialMboxes.php::_getSpecialUse()
does not set the 'sort_delimiter'.
This is just a tracking bug so the issue won't get lost.
Thomas