unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Charles Philip Chan <cpchan@bell.net>
To: help-gnu-emacs@gnu.org
Subject: Re: What are Emacs best uses?
Date: Sat, 17 Aug 2013 16:20:24 -0400	[thread overview]
Message-ID: <87a9kgf4s7.fsf@karnak.MagnumOpus.khem> (raw)
In-Reply-To: CAJR3QneWnP+Tvs-ez5RnRoqxkZ0vp6cs2wOMuq6dpQtxDTYK_w@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

Jorge <1gato0a@gmail.com> writes:

Hi Jorge:

>   But gmail allows multiple labels per conversation(thread).  Does
> this not confuse Emacs?  Also, does Emacs group threads differently
> from Gmail, meaning that you see a different thing in Emacs than what
> you see in the web interface?  Does this cause problems?  Is there any
> potential for data loss?

This will answer all your questions:

     https://support.google.com/mail/answer/77657?hl=en

Personally I don't use the web interface- I detest web mail. I prefer to
download my emails from my various online accounts via pop3 with
fetchmail. They are then feed to procmail for splitting (a hand crafted
.promailrc which include a dynamic procmail config file generated by
niko-bbdb-split.el[1] and with spamassasin integration). The emails are
put into the various folders via dovecot's dovecot-lda command in a
maildir hierarchy. I can then read my email from anywhere by connecting
to my home dovecot server via imaps.

Charles

Footnotes: 
[1] http://osdir.com/ml/bbdb/2012-08/msg00068.html 

-- 
"However, complexity is not always the enemy."

  -- Larry Wall (Open Sources, 1999 O'Reilly and Associates)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2013-08-17 20:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 17:05 What are Emacs best uses? Jorge
2013-08-12 18:52 ` Peter Dyballa
2013-08-13  4:04 ` Charles Philip Chan
2013-08-17 14:11   ` Jorge
2013-08-17 20:20     ` Charles Philip Chan [this message]
2013-08-18 10:31       ` Jorge
2013-08-19 11:09         ` Phillip Lord
2013-08-19 20:21         ` Charles Philip Chan
2013-08-19  2:46     ` Eric Abrahamsen
2013-08-13 11:30 ` Phillip Lord
2013-08-13 14:43   ` Drew Adams
2013-08-13 16:05 ` W. Greenhouse
2013-08-14  8:21   ` Thomas Shannon
2013-08-15 14:41     ` W. Greenhouse
2013-08-16  9:49       ` Thomas Shannon
2013-08-14 14:51 ` Ken Goldman
2013-08-14 19:04 ` Nikolay Kudryavtsev
2013-08-19 13:52 ` Luca Ferrari
     [not found] ` <mailman.340.1376920365.10748.help-gnu-emacs@gnu.org>
2013-08-19 14:04   ` Sebastien Vauban
2013-08-19 14:35     ` Luca Ferrari
     [not found]     ` <mailman.342.1376922920.10748.help-gnu-emacs@gnu.org>
2013-08-20  8:25       ` Sebastien Vauban
2013-08-20 10:56         ` Luca Ferrari
     [not found]         ` <mailman.401.1376996210.10748.help-gnu-emacs@gnu.org>
2013-08-20 12:44           ` Sebastien Vauban
2013-08-21  1:58       ` Jason Rumney
2013-08-21  6:25         ` Luca Ferrari
     [not found] <mailman.3062.1376327401.12400.help-gnu-emacs@gnu.org>
2013-08-12 18:08 ` Pascal J. Bourguignon
2013-08-12 18:45   ` Andreas Röhler
2013-08-13 13:34   ` Joe Corneli
2013-08-13  1:52 ` Emanuel Berg
2013-08-13  3:29 ` Rustom Mody
2013-08-13 11:52 ` Dan Espen
2013-08-13 12:27   ` Filipp Gunbin
     [not found]   ` <mailman.3116.1376396894.12400.help-gnu-emacs@gnu.org>
2013-08-13 12:33     ` Dan Espen

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=87a9kgf4s7.fsf@karnak.MagnumOpus.khem \
    --to=cpchan@bell.net \
    --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).