Re: Confusing message from notmuch-maildir-fcc-with-notmuch-insert
I have encountered that message several times, and in my case, just creating the directory is not a good solution. My use case is that I have several email accounts in the same notmuch database that I want to treat separately (personal gmail, personal non-gmail, work...). I encounter this error when I manually change the sending address (it defaults to the one used most often) and then the FCC does not match properly. I use the error to signal that I should edit the FCC line as well. This was an accident, as I did not originally intend to use the error to catch my mistakes and sometimes it cannot detect that. But just creating extra directories would be worse from my POV. I do agree a clearer error message would be helpful (it took me a while to figure out the email is actually sent before the error and I should not resend). Thanks for all your combined efforts! Miguel ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: Confusing message from notmuch-maildir-fcc-with-notmuch-insert
Carl Worth writes: > > Certainly if the code had just created the directory for me, everything > would have been fine. But I guess I can understand why the code doesn't > do that if we're trying to support a case where users are manually > typing random strings in for the Fcc header and might typo something? I > don't know how much I _really_ care about that use case, (if notmuch > creates a directory based on a typo the mail will still be indexed and > perhaps some notmuch users don't care much about directory names inside > the mail store). > > Otherwise, if the message had said: > > Failed to save sent message in local mail store. Directory > /home/cworth/mail/sent does not exist. Create? (y/n) > > Then I definitely would have understood the message and things would > have been much smoother for me. > I agree your message is clearer, if the only possible failure is a missing directory. I'm not sure if that's the case though. Probably a first step is to make sure a sensible description of the error is reported by notmuch insert and made available to the user. d ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
