Gnus development mailing list
 help / color / mirror / Atom feed
From: Alberto Luaces <aluaces@udc.es>
To: ding@gnus.org
Subject: Re: gmail setup
Date: Tue, 07 Apr 2020 20:35:02 +0200	[thread overview]
Message-ID: <87imibuotl.fsf@eps142.cdf.udc.es> (raw)
In-Reply-To: <87lfn7gnvq.fsf@dick>

dick.r.chiang:

> AL> Correction: more than 200 *unread* messages.
>
> The "How many articles" question is asked when accessing an inbox
> that has N unreads where N is either zero or a number greater than
> gnus-large-newsgroup.  People more than occasionally access their inbox
> when N is zero.
>

Strange use case you have there: I don't do that.  If I wanted to access
a group with zero unread messages, I would search (with nnnir, for
example) instead.  And, by the way, let's not forget the excellent
dianyou!  (https://github.com/redguardtoo/dianyou)

>
> AL> I have managed in the past to use gnus without writing any configuration
> AL> myself — just creating an nnimap server with "e" from the server window
> AL> and filling the parameters needed
>
> With respect, this is "over the heads" of most users.  The "*Server*"
> buffer somewhat "trickily" accessed via "^" is already a headscratcher (it was
> for me!) for people accustomed to mainstream mail clients.
>

It is in the manual, which is the supposedly is the primary source of
information, over those blog posts that can be not so exhaustive, or
even incomplete.

But my point was that setting an nnimap server usually is best done with
the less parameters the better.

>
> I admit that complaining does not advance Gnus's cause.  In my
>defense, I've
> published a talk-is-cheap-show-me-the-code primer to Gnus IMAP
> (https://github.com/dickmao/gnus-imap-walkthrough),

Thanks for that!  Looks interesting.

>but removing
> "A Practical Guide to Gnus" from its lofty throne atop Google's results is all
> but impossible at this point.
>

Well, you can also either change your email provider and/or your web
search engine.  Yes, I do have a gmail account, but nowadays is not my
primary address, and have almost nothing in there.  I moved to more
standard-caring hosts (almost anyone but google).

-- 
Alberto



  reply	other threads:[~2020-04-07 18:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 14:33 how to forward a message that contains attachment Uwe Brauer
2020-04-04 14:54 ` Eric S Fraga
2020-04-04 18:57   ` Uwe Brauer
2020-04-05  2:00     ` Bob Newell
2020-04-05  6:07       ` Uwe Brauer
2020-04-05 19:31         ` Bob Newell
2020-04-05 13:18     ` Eric S Fraga
2020-04-05 17:11       ` Uwe Brauer
2020-04-05 17:37         ` Adam Sjøgren
2020-04-05 21:25           ` dick.r.chiang
2020-04-06 10:19             ` gmail setup (was: how to forward a message that contains attachment) Alberto Luaces
2020-04-07 16:42               ` gmail setup dick.r.chiang
2020-04-07 17:46                 ` Alberto Luaces
2020-04-07 18:19                   ` dick.r.chiang
2020-04-07 18:35                     ` Alberto Luaces [this message]
2020-04-08  1:53                       ` Bob Newell
2020-04-10 16:56                         ` Alberto Luaces
2020-04-06 10:19           ` how to forward a message that contains attachment Uwe Brauer
2020-04-06 10:26           ` Uwe Brauer
2020-04-07 17:03             ` Adam Sjøgren
2020-04-06 11:36           ` Uwe Brauer

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=87imibuotl.fsf@eps142.cdf.udc.es \
    --to=aluaces@udc.es \
    --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).