Gnus development mailing list
 help / color / mirror / Atom feed
From: Bob Newell <bobnewell@bobnewell.net>
To: ding@gnus.org
Subject: Re: Annoying issue with group not showing new messages
Date: Sun, 21 Feb 2021 10:41:38 -1000	[thread overview]
Message-ID: <87sg5p8871.fsf@emailmessageidheader.nil> (raw)
In-Reply-To: <87czwtjo80.fsf@dick> (dick r. chiang's message of "Sun, 21 Feb 2021 12:59:59 -0500")


dick.r.chiang@gmail.com writes:

> All good, sir, although I often wonder how non-lispers find their way to gnus,
> that most ornery of mail user agents ...

> Still, even in the 90s, gnus would have to be considered a highly niche
> offering with respect to mailx, pine, elm, or even
> emacs-based RMAIL.

Aloha,

I don't argue with any of what you say. Gnus is definitely
ornery and requires up-front and ongoing study and indeed
often a non-trivial amount of elisp-foo. I remember pine well;
yes, it was dead simple. Today mutt is not a lot more
complicated for basic use, which probably comprises 90% of use
cases.

But gnus can do /anything/ if you have the patience and are
willing to work at developing the necessary skills. This of
course just amplifies your statement about non-lispers (and
probably 99.99% of the world) not finding their way to Gnus.

So yes, it's a niche product (and in so saying I do /not/
intend to imply even the slightest trace of elitism). It's for
explorers and tinkerers who are willing to spend the time
required to make Gnus sing and dance and do amazing things.

Of course, there is a dark side. I don't believe any real Gnus
afficionado can say that they haven't spent time on Gnus that
could have been more profitably spent on other things. I know
I have, in spades. But the challenge is hard to resist. Hours
pass because I /know/ I can get Gnus to do x-y-z. And
eventually I succeed. Gnus will do x-y-z. Let's just hope that
x-y-z is something that I actually have a need for!

-- 
Bob Newell
Honolulu, Hawai`i

- Via GNU/Linux/Emacs/Gnus/BBDB


  reply	other threads:[~2021-02-21 20:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 12:06 Luis Henriques
2021-02-19 12:50 ` dick.r.chiang
2021-02-21 17:38   ` Luis Henriques
2021-02-21 17:59     ` dick.r.chiang
2021-02-21 20:41       ` Bob Newell [this message]
2021-02-21 22:29     ` Eric Abrahamsen

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=87sg5p8871.fsf@emailmessageidheader.nil \
    --to=bobnewell@bobnewell.net \
    --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).