From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Gnus encouragement of GMail (was: Installation, activation and setup of packages (e.g. Gnus))
Date: Tue, 5 Jan 2010 16:28:41 -0600 [thread overview]
Message-ID: <87zl4sb2zq.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <jwv7hrwl55y.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 05 Jan 2010 14:43:33 -0500")
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.devel as well.
On Tue, 05 Jan 2010 14:43:33 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> Ted Z wrote:
>> GMail should have a specific setup path since it's so popular.
SM> I definitely do not want Emacs to encourage the use of GMail over
SM> any other service.
Well, users are constantly pointed to the relevant EmacsWiki page for
GMail support in Gnus. The settings required are not intuitive. So we
either accept the support burden and frustrated users, or we give them
the sensible settings as I suggested, or we point them to the
EmacsWiki.
I don't think the second and third options encourage GMail use in
particular. They are just tweaks for those who use GMail IMAP. GMail
is the only major IMAP provider to require well-known tweaks; when
others arise we'll handle them.
Similarly, there's code in Gnus to address Exchange IMAP issues; does
that encourage Exchange use? I don't think so. IMHO it actually
broadens the appeal of free software to support Exchange IMAP better.
I guess a fourth option is to write gnus-gmail.el, host it externally,
and make it clear that it's not endorsed by the FSF. But that's no
better--how will the users know they need gnus-gmail.el? I'd rather
include the support and make it clear it's not an endorsement.
Ted
parent reply other threads:[~2010-01-05 22:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <jwv7hrwl55y.fsf-monnier+emacs@gnu.org>]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zl4sb2zq.fsf_-_@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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 NNTP newsgroup(s).