Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: assistants, again
Date: Wed, 20 Oct 2010 10:12:48 -0500	[thread overview]
Message-ID: <87ocaolwy7.fsf@lifelogs.com> (raw)
In-Reply-To: <8762wxcb8q.fsf@lifelogs.com>

On Wed, 20 Oct 2010 07:14:13 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> On Tue, 19 Oct 2010 14:01:31 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 
>>>> I don't know how to use assistant.el well (it's been years since you
>>>> wrote it) but I think it's reasonable to check if this is the first time
>>>> someone starts Gnus and then run assistants accordingly.  We should
>>>> provide assistants to:
>>>> 
>>>> - set up mail servers (providing a fast path for GMail and other popular
>>>> ones)
>>>> 
>>>> - set up NNTP servers (including GMane and GWene)
>>>> 
>>>> - set up archiving, expiry, spam.el, gnus-registry, gnus-sync, etc. (I'm
>>>> listing just my ideas, this should be everything useful)

TZ> - also set gnus-blocked-images to something other than "." because the
TZ>   default is really annoying (but the user needs to approve in case they
TZ>   are paranoid)

- also set the HTML renderer to mm-shr or something else

(yes, this is turning into a TODO list, feel free to add other things)

Ted




  reply	other threads:[~2010-10-20 15:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  5:07 make it easier to use nnml for archive groups Dan Nicolaescu
2010-10-14 18:05 ` Lars Magne Ingebrigtsen
2010-10-15 14:50   ` Dan Nicolaescu
2010-10-16 18:15     ` Lars Magne Ingebrigtsen
2010-10-18  7:34       ` Dan Nicolaescu
2010-10-18 19:13         ` Lars Magne Ingebrigtsen
2010-10-19 14:20           ` Ted Zlatanov
2010-10-19 18:22             ` Lars Magne Ingebrigtsen
2010-10-19 18:37               ` Ted Zlatanov
2010-10-19 18:50                 ` Lars Magne Ingebrigtsen
2010-10-19 19:01                   ` assistants, again (was: make it easier to use nnml for archive groups) Ted Zlatanov
2010-10-19 19:08                     ` assistants, again Lars Magne Ingebrigtsen
2010-10-19 19:21                       ` Ted Zlatanov
2010-10-19 19:30                         ` Lars Magne Ingebrigtsen
2010-10-20 12:14                     ` Ted Zlatanov
2010-10-20 15:12                       ` Ted Zlatanov [this message]
2010-10-20 15:33                         ` Julien Danjou
2010-10-20 16:16                           ` Ted Zlatanov
2010-10-20 16:42                             ` Lars Magne Ingebrigtsen
2010-10-20 16:58                               ` Ted Zlatanov
2010-10-20 17:16                               ` Lars Magne Ingebrigtsen
2010-10-20 16:40                       ` Lars Magne Ingebrigtsen
2010-10-19 19:41               ` make it easier to use nnml for archive groups Andreas Schwab
2010-10-20  6:31                 ` Reiner Steib
2010-10-20 14:59                   ` Ted Zlatanov
2010-10-20 15:32                     ` Dan Nicolaescu
2010-10-20 16:12                       ` Ted Zlatanov
2010-10-20 16:19                     ` Robert Pluim
2010-10-21  1:22                     ` Lars Magne Ingebrigtsen
2010-10-21  1:21                   ` Lars Magne Ingebrigtsen
2010-10-20 15:29               ` Dan Nicolaescu

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=87ocaolwy7.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).