From: Peter Davis <pfd@pfdstudio.com>
To: emacs-orgmode@gnu.org
Subject: Re: [OFF TOPIC] almost giving up on emacs email..looking for advice?
Date: Tue, 11 Aug 2015 10:16:13 -0400 [thread overview]
Message-ID: <6sw6c7oaidzz9u.fsf@dhcp-6-148.hmco.com> (raw)
In-Reply-To: 55C9FE6A.708@gmail.com
Scott Randby <srandby@gmail.com> writes:
> On 08/11/2015 08:23 AM, Peter Davis wrote:
>>
>> 2) I need a decent editor for replies. I have not found a
>> browser-based client that has this.
>
> For me, setting up any of the Emacs email clients to work properly
> with my various email tasks is a daunting task. This especially true
> for my work email account which is not a Gmail account. I simply don't
> have the technical knowledge to get everything working, and I don't
> have the time to acquire that technical knowledge.
This has certainly been the case for me with gnus. I spent years (literally) playing with gnus and giving up, only to be drawn back
to it weeks, months or years later to try again. Seriously, it was only after years of this that I managed to get things working
well enough to actually use gnus, and even at that I only use it with IMAP.
FWIW, I also used VM for a while (easier to configure, but much less powerful), MH-E, Wanderlust as well as non-Emacs clients
(Sylpheed, mutt, Thunderbird, and others.) It's a crowded field. I generally liked some things about each of these, and disliked
others. There's no perfect solution.
One of the persistent frustrations for me with Thunderbird is that it still, even years after the problem was reported, can't get
the unread counts correct for various folders all the time. It frequently shows unread counts for folders that have no unread
messages, and vice versa.
I get hundreds of messages a day, so I like to just be able to plow through them quickly, replying as needed, flagging some for
later attention, etc. Mutt was actually the fastest for that, but I hate the way it displays HTML messages with w3m in dump
mode. Mutt is also pretty challenging to configure, and that has to be re-created for each new machine. With gnus, I just copy my
.gnus.el file over and, bam, done.
-pd
next prev parent reply other threads:[~2015-08-11 14:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 12:43 [OFF TOPIC] almost giving up on emacs email..looking for advice? Xebar Saram
2015-08-06 12:50 ` Peter Davis
2015-08-06 13:56 ` Eric S Fraga
2015-08-06 14:31 ` John Kitchin
2015-08-06 16:50 ` Titus von der Malsburg
2015-08-06 17:21 ` Xebar Saram
2015-08-06 20:45 ` Suvayu Ali
2015-08-06 15:59 ` Jorge A. Alfaro-Murillo
2015-08-06 23:51 ` Ramon Diaz-Uriarte
2015-08-08 3:38 ` Peter Salazar
2015-08-11 10:04 ` Fabrice Popineau
2015-08-11 12:23 ` Peter Davis
2015-08-11 12:30 ` Fabrice Popineau
2015-08-11 12:38 ` Rasmus
2015-08-11 12:35 ` Nicolas Richard
2015-08-11 13:20 ` Suvayu Ali
2015-08-11 13:53 ` Scott Randby
2015-08-11 14:16 ` Peter Davis [this message]
2015-08-11 14:38 ` Xebar Saram
2015-08-11 14:51 ` Scott Randby
2015-08-12 3:13 ` Peter Salazar
2015-08-12 4:30 ` Eric Abrahamsen
2015-08-12 8:34 ` Rasmus
2015-08-12 9:09 ` Eric Abrahamsen
2015-08-12 9:35 ` Rasmus
2015-08-12 13:36 ` Eric Abrahamsen
2015-08-12 22:42 ` Rasmus
2015-08-13 2:10 ` Eric Abrahamsen
2015-08-11 13:22 ` Matt Lundin
2015-08-15 7:37 ` Bastien Guerry
2015-08-15 12:35 ` Matt Lundin
2015-08-18 16:36 ` Bastien
2015-08-11 14:00 ` Gerald Wildgruber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6sw6c7oaidzz9u.fsf@dhcp-6-148.hmco.com \
--to=pfd@pfdstudio.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).