From: Karl Fogel <kfogel@red-bean.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: Re: Why does Gnus article-moving act like a fetch of new news?
Date: Fri, 09 Apr 2021 23:58:32 -0500 [thread overview]
Message-ID: <87wnta91mv.fsf@red-bean.com> (raw)
In-Reply-To: <874kgekcd3.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 09 Apr 2021 21:11:20 -0700")
On 09 Apr 2021, Eric Abrahamsen wrote:
> I think an argument could be made that if the DONT-SCAN optional
> argument is non-nil, we should also skip running the two
> get-new-news hooks. But let's see what Lars says.
You mean the second argument to
`gnus-group-get-new-news-this-group'?
The doc string is somewhat confusing on that argument:
| gnus-group-get-new-news-this-group is an interactive compiled
| Lisp function in ‘gnus-group.el’. | |
(gnus-group-get-new-news-this-group &optional N DONT-SCAN) | |
Check for newly arrived news in the current group (and the N-1
next groups). | The difference between N and the number of
newsgroup checked is returned. | If N is negative, this group
and the N-1 previous groups will be checked. | If DONT-SCAN is
non-nil, scan non-activated groups as well.
In other words, the meaning of "DONT-SCAN" seems to be: scan! One
can see how a person might be confused by this :-).
According to the "Terminology" section in the Gnus manual,
"activating" a group means this:
| The act of asking the server for info on a group and computing
the | number of unread articles is called “activating the
group”. | Un-activated groups are listed with ‘*’ in the group
buffer.
Thus I don't understand why moving an article to a group should
unconditionally "activate" that group in the first place. I can
see how moving an *unread* article to a group might activate that
group? But the code in `gnus-summary-move-article' doesn't have
such a conditional.
And even if we leave aside the question of why we unconditionally
activate the destination group, it's still not clear why
activating a group should imply getting new news for that group.
Or, to put it another way: why is the way to activate a group to
get new news for it? These just seem like two very different
things.
I realize you may not know the answers either, and that we may
need Lars or someone with a similar level of knowledge. I'm just
trying to line up some useful questions. Gnus is a very, very
complex code base, I have learned through several dives in its
coastal waters.
Best regards,
-Karl
next prev parent reply other threads:[~2021-04-10 4:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 21:47 Why does Gnus article-moving act like a fetch of new news? Karl Fogel
2021-04-10 4:11 ` Eric Abrahamsen
2021-04-10 4:58 ` Karl Fogel [this message]
2021-04-10 5:29 ` Eric Abrahamsen
2021-04-10 8:29 ` Andreas Schwab
2021-04-10 13:06 ` Stefan Monnier
2021-04-10 22:00 ` Eric Abrahamsen
2021-04-11 6:02 ` Karl Fogel
2021-04-11 16:05 ` Lars Ingebrigtsen
2021-04-12 17:05 ` Eric Abrahamsen
2021-04-12 17:56 ` Karl Fogel
2021-04-12 18:26 ` Eric Abrahamsen
2021-04-13 20:25 ` Karl Fogel
2021-04-13 21:59 ` Eric Abrahamsen
2021-04-14 3:27 ` Karl Fogel
2021-04-25 17:37 ` Lars Ingebrigtsen
2021-05-03 20:52 ` Eric Abrahamsen
2021-05-03 20:53 ` Eric Abrahamsen
2021-05-05 23:21 ` Karl Fogel
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=87wnta91mv.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).