From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [OFF TOPIC] almost giving up on emacs email..looking for advice?
Date: Thu, 6 Aug 2015 22:45:12 +0200 [thread overview]
Message-ID: <20150806204512.GB28462@chitra.no-ip.org> (raw)
In-Reply-To: <CAOQHXPqL_OSwNbzeJ2Px9W-_xTYZt+Vf5Di9yOpSgLXxVsgoMw@mail.gmail.com>
On Thu, Aug 06, 2015 at 08:21:15PM +0300, Xebar Saram wrote:
> thank so much everyone for your great tips and comments
>
> you gave me more energy to further pursue gnus and or mu4e
There is also notmuch. In fact, notmuch seems to have an edge over mu4e
when it comes to performance, at least that's my understanding.
I would like to say something though. I think you should not blindly
keep on trying all these options, that would probably end up in
frustration all over again. First you need to answer, how you use
email, how do you want to access it, and what kind of features do you
want. You shouldn't limit yourself to Emacs either. Eventhough Emacs
can do many things, often there are other tools which are better suited.
- Email could be a means for discussions, in that case it's a reference
- Then you might want searchability, or someway to refer back to
messages.
- It could be a todo list for you, in that case you want some way to
filter and carry over your emails to your todo lists.
- Do you want filtering for other purposes?
- You might want access to your emails over IMAP (it's immediate), or
available locally (always there, not immediate).
- Local disk space constraints.
- Do you want access to your emails from multiple interfaces?
- Do you prefer using the terminal or a GUI?
As you see, there are lots of points to think about.
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2015-08-06 20:45 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 [this message]
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
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=20150806204512.GB28462@chitra.no-ip.org \
--to=fatkasuvayu+linux@gmail.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).