-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flag more inline attachements than just images. #63
Comments
You mean scanning attached pdf documents during 'mu index'? |
I don't mean the pdf's contents, but if the file is inlined ( I hope that clarifies it a little :-) |
Sure, thanks. I've pushed some changes, which hopefully help wrt the mu4e part of this. |
Ok, this should be fixed in git. |
I stll have a problem with inline attachments in 0.9.9.5-dev4. Attachments with the following headers neither flag the message with 'a', nor do the show up in the message body (i.e. they are absolutely invisible without using mu4e-view-raw-message): Content-Disposition: inline; filename="review-diff.txt" |
Can you attach an example message file that has this problem? Thanks! |
Not sure how to properly attach files on github. Hope this will work: https://gist.github.com/4107377 In that email, there's no way to read (or even know it exists) review-diff.txt other than mu4e-view-raw-message. |
Sadly, that didn't work (I get a 20 byte file from that link). Can you send it to me through normal email? Thanks. |
Sorry, I have updated that link, it should have the email contents now. I also did some quick tests. It appears that the root cause is a combination of "text/x-diff" for the Content-Type header and "inline" for Content-Disposition. Sending "text/plain" attachments inline works just fine, i.e. they are both indexed and visible in the mu4e message view. |
Thanks -- I've made a change, hopefully in the latest git, it is fixed. |
Closing. |
Apple Mail inlines different kinds of attachments, e.g. PDF documents. It would be great to see them indexed and flagged as attachments too.
I managed to include them with mu4e by changing parts of
mu4e~view-construct-attachments-header
[1], but to make it perfect they should be searchable.[1]
The text was updated successfully, but these errors were encountered: