From: Julien Cubizolles <j.cubizolles@free.fr>
To: help-gnu-emacs@gnu.org
Subject: From Gnus to mu4e
Date: Thu, 20 Aug 2015 23:23:36 +0200 [thread overview]
Message-ID: <87d1yhpsbr.fsf@free.fr> (raw)
I'm considering moving from Gnus to mu4e, mostly because I spend too
much time tinkering with settings I don't really understand/need in
Gnus, and because the search feature seems promising. If some of you
have already made such a move, or are just happy users of mu4e, I'd
appreciate your input on the following issues.
* Can OfflineImap or whatever imap sync tool used exclude some folders
in the main Maildir folder from being synced to the IMAP server ? I'd
like to be able to archive some old mail without it being sent to
Gmail.
* I'm using gmane to read a lot of mailing lists. I guess there's no way
to do that with mu4e and I'm considering sticking with Gnus for that
use. Does that seem like a reasonable solution ?
* Can mu4e use the Gmail labels for search queries ?
* If a message is tagged with several labels on Gmail, does it appear in
several folders in the local repository ? On a related note, if one
were to move a message from a folder in a repository synced with Gmail
to another folder not synced (for archiving purposes), I guess the
message would remain at least in the [Gmail]/All Mail folder. Is there
an easy way to remove it altogether from Gmail ?
* Finally, the mailing list for mu4e doesn't seem very active
(especially when you compare it to the one for gnus). Are there any
other channels to get some help ?
Thanks for your input.
Julien.
next reply other threads:[~2015-08-20 21:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 21:23 Julien Cubizolles [this message]
2015-08-21 10:28 ` From Gnus to mu4e Julien Cubizolles
2015-08-21 10:49 ` Colin Yates
2015-08-21 13:06 ` Suvayu Ali
2015-08-26 6:53 ` Julien Cubizolles
2015-08-25 5:49 ` Bastien
2015-08-25 6:28 ` Ian Zimmerman
2015-08-25 6:56 ` Bastien Guerry
2015-08-26 7:22 ` Julien Cubizolles
2015-08-27 12:50 ` Rainer M Krug
2015-08-27 17:15 ` Bastien
2015-08-28 8:39 ` Rainer M Krug
2015-08-28 8:44 ` Bastien
2015-08-28 8:51 ` Rainer M Krug
2015-08-28 8:58 ` Rasmus
2015-08-28 9:15 ` Julien Cubizolles
2015-08-28 10:03 ` Rainer M Krug
2015-08-28 10:08 ` Rasmus
2015-08-28 10:41 ` Rainer M Krug
2015-08-28 10:04 ` Rasmus
2015-08-28 8:51 ` Bastien
2015-08-27 21:27 ` Julien Cubizolles
2015-08-27 23:34 ` Suvayu Ali
2015-08-27 23:50 ` Ian Zimmerman
2015-08-28 0:14 ` Suvayu Ali
2015-08-28 0:24 ` Ian Zimmerman
2015-08-28 8:25 ` Rainer M Krug
2015-08-28 9:06 ` Suvayu Ali
2015-08-28 15:31 ` Ian Zimmerman
2015-08-31 0:16 ` Suvayu Ali
2015-08-28 8:21 ` Rainer M Krug
2015-08-27 12:58 ` Suvayu Ali
2015-08-27 15:52 ` Glenn Morris
2015-08-27 17:32 ` Suvayu Ali
2015-08-27 17:11 ` Bastien
2015-08-27 17:08 ` Bastien
2015-08-27 17:30 ` Suvayu Ali
2015-08-27 21:52 ` Julien Cubizolles
2015-08-27 22:18 ` Bastien
2015-08-27 23:30 ` Julien Cubizolles
[not found] <mailman.14.1440105837.31004.help-gnu-emacs@gnu.org>
2015-08-24 11:19 ` Joost Kremers
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1yhpsbr.fsf@free.fr \
--to=j.cubizolles@free.fr \
--cc=help-gnu-emacs@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.
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).