41–50 of 246 posts
Mind you, that's on a secondary email account; if I need to handle images or attachments I forward it to gmail.
Earlier quoted context omitted.
the only images i find are either from spammy adverts or tracking pixels. Normal people don't put images in emails. As for attachments, you can open them in their native programs just fine.
Normal people then don't use email for creative work involving designs, mockups, sketches, etc. And yes, it kind of sucks to have the image opened out of its context in new window. Did you notice how HTML got successful by interleaving text and images?
Sure they do, by attaching them.
This is all very nice, but the fact that the article doesn't even _mention_ images or attachments shows how divorced it is from the reality of most people's email experience. I happily used emacs as my mail-reader from 1989 to about 2009 (first RMAIL mode, then VM). The increasing importance of non-text formats made it cumbersome, and I somewhat reluctantly switched to GMail. It's hard to imagine switching back now.
the only images i find are either from spammy adverts or tracking pixels. Normal people don't put images in emails. As for attachments, you can open them in their native programs just fine.
Email clients like gmail/outlook put images in the content of the email (NOT an attachment) when you drag/drop files onto the window or when you copy/paste a picture inside the mail.
There was a time when this all went to attachment, that is not the case anymore.
Earlier quoted context omitted.
the only images i find are either from spammy adverts or tracking pixels. Normal people don't put images in emails. As for attachments, you can open them in their native programs just fine.
Normal people absolutely put images in their emails. Email clients like gmail/outlook put images in the content of the email (NOT an attachment) when you drag/drop files onto the window or when you copy/paste a picture inside the mail. There was a time when this all went to attachment, that is not the case anymore.
Sure it can be cumbersome if the various images are interleaved with commentary, but in my experience 99% of the time it's "Here are the pictures/documents you wanted" followed by a few attachments (inline or not).
There's a very, very small proportion of emails where HTML is actually mandatory to make sense of the contents. And for those I can just tell mutt to load the HTML in my web browser. I very seldom have to do that though, not enough to be a real nuisance.
This is all very nice, but the fact that the article doesn't even _mention_ images or attachments shows how divorced it is from the reality of most people's email experience. I happily used emacs as my mail-reader from 1989 to about 2009 (first RMAIL mode, then VM). The increasing importance of non-text formats made it cumbersome, and I somewhat reluctantly switched to GMail. It's hard to imagine switching back now.
Richard Stallman (RMS) uses emacs for email as well. I can't imagine it. Too much valuable information comes in the form of rich emails for me to even try.
Earlier quoted context omitted.
Normal people then don't use email for creative work involving designs, mockups, sketches, etc. And yes, it kind of sucks to have the image opened out of its context in new window. Did you notice how HTML got successful by interleaving text and images?
> Normal people then don't use email for creative work involving designs, mockups, sketches, etc. Sure they do, by attaching them.
So i just did to test, and it is horrible! :)
Interestingly, I went the other way. I used to have mutt for years, then went through a dark phase (macOS Mail.app, Evernote and Things) and finally concluded to Emacs with mu4e. Integrating mail with Emacs was the best idea ever, because Emails include either todos or serve as reference in projects. Creating todos from Mails as well as linking to them from org-mode is only a shortcut away. I have never had a more ea…
I have also been using an emacs (spacemacs) + org + mu4e setup for 6 months or so. Unfortunately, everything seems to be really buggy and break at random moments. Also, there isn't a really good iOS integration story. So, I am slowly retracting and going back to vim, Mail.app, Things (and mutt every now and then ;)).
I'm not trying to be mean, it's a great project, of course.
I have my own configuration on top of vanilla Emacs and have never had any problems with things stopping to work.
As for iOS I don't need more than what MobileOrg has. I need to add new todos and very seldom look stuff up. Both work totally fine. And I'm saying this after having been a paying Evernote and Things user for years^^
Very good. I could easily complement this with a calendar terminal app. Anyone knows of a terminal calendar app to keep appointments ? (similar to the apple calendar, or google calendar)
Interestingly, I went the other way. I used to have mutt for years, then went through a dark phase (macOS Mail.app, Evernote and Things) and finally concluded to Emacs with mu4e. Integrating mail with Emacs was the best idea ever, because Emails include either todos or serve as reference in projects. Creating todos from Mails as well as linking to them from org-mode is only a shortcut away. I have never had a more ea…
for me the only thing that i found that worked is Zero Inbox. i get a lot e-mail per day, most of them are not actionable ( notifications, statuses, replays for other departments and so on ) i archive them, and the ones that i have to handle are moved to wunderlist or replayed right away. this is the only solution that i found to work for me. I know that i have to handle it now inside wunderlist. but it works ok for…
But my links to mail from Things and EN kept breaking. I also work with Inbox Zero and that's the primary reason for my switch - without references it got worthless.