From: Xebar Saram <zeltakc@gmail.com>
To: Peter Davis <pfd@pfdstudio.com>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: [OFF TOPIC] almost giving up on emacs email..looking for advice?
Date: Tue, 11 Aug 2015 17:38:29 +0300 [thread overview]
Message-ID: <CAOQHXPo5ea3fHrck0AfyvvddxtAwoJnxEvkps=8-Cv18xizbsQ@mail.gmail.com> (raw)
In-Reply-To: <6sw6c7oaidzz9u.fsf@dhcp-6-148.hmco.com>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On Tue, Aug 11, 2015 at 5:16 PM, Peter Davis <pfd@pfdstudio.com> wrote:
> 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.
>
Hehe this is *exactly* what i have experienced. im dying to move over to
emacs for emails but so far both gnus and mu4e are giving me so many issues
(and it may be that im just not smart enough to configure them properly).
The latest i tried was setting up gnus via imap (gmail ) which worked for
approximately 2 hours before getting errors and making me (once again..)
give up and crawl back defeated to gmail :) plus the fact that i need a
separate emacs session just for mail and all other small quirks in gnus are
kind of a pain to setup (at least it seems so).
mu4e seemed so promising but for me it seems that no matter what i do i
cant get the headers to auto refresh when i get a new email which is
driving me crazy so had to give up on that.
Z
[-- Attachment #2: Type: text/html, Size: 2080 bytes --]
next prev parent reply other threads:[~2015-08-11 14:38 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
2015-08-11 14:38 ` Xebar Saram [this message]
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='CAOQHXPo5ea3fHrck0AfyvvddxtAwoJnxEvkps=8-Cv18xizbsQ@mail.gmail.com' \
--to=zeltakc@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=pfd@pfdstudio.com \
/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).