[Users] [Bug 3212] When msgnum matches a sub-folder name, fetch fails

noreply at thewildbeast.co.uk noreply at thewildbeast.co.uk
Sun Jun 15 04:52:29 CEST 2014


http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3212

--- Comment #1 from Pierre Fortin <pf at pfortin.com> ---
Namespace collision looks like a good catch...

I too have lots of 20xx folders[1]...  sounds like flagging the directory names
is needed, such as adding a:
- leading "." -- I don't like this one since that 'hides' those names.
- trailing ".d" (very common in Linux) when the name is all numeric 
  (or always); but hiding the ".d" in the folder list.

Oh my!  Starting to visualize all the places code might be affected; unless a
low-level function hides this from the main code...

[1] in my case, all msgnums were already >=2014 when I created most of my
yearly archives; so I wasn't affected.

Whoa!  I should have seen collisions while _creating_ my folders....

AH-HA!!  My structure is:

MainFolderName
  Archives <== this contains only yearly directories; no messages.
    20xx
    20yy

I must have done that to reduce the sub-folders shown during expansions when I
have many archive sub-folders... and fortuitously avoided this bug.

Jeroen: would that be a satisfactory solution or workaround?  Although I would
suggest an error dialog:

       /!\  Error: all-numeric folder names not allowed
            in directories containing messages.

Argh! the more I think about this, the messier it gets...  my structure above
is only valid as long as I never expect to include messages with conflicting
names; such as via:
- drag & drop
- filtering/actions
- 'save here' compose

That would like require disallowing messages going into folders containing
numeric folders....  mutually exclusive...

HTH

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Users mailing list