Re: Should nnatom default to offline when unplugged?

Daniel Semyonov wrote:

>>>>>> James Thomas writes:
>
>     > Daniel Semyonov wrote:
>     >>>>>>> James Thomas writes:
>     >>
>     >> > Hi all,
>     >> > Right now I use something like this for
>     >> > 'nnatom-read-feed-function':
>     >>
>     >> > (defun my/nnatom-read-feed-function (url &rest args)
>     >> >   (if gnus-plugged (nnatom--read-feed url nil)
>     >> >       '(title nil nil subtitle nil nil)))
>     >>
>     >> > ...for when I start with 'gnus-unplugged' for offline
>     >> > reading. I was
>     >> > wondering if something like this could/should be made the
>     >> > default -
>     >> > anyone wanting the existing behavior (why?) could let-bind
>     >> > gnus-plugged
>     >> > in a similar function. But it could have interactions if
>     >> > agentization is
>     >> > ever needed...
>     >>
>     >> I honestly never use Gnus unplugged so I may be misunderstanding
>     >> something, but AFAICT only agentized servers are supposed to
>     >> be affected by it (according to my brief usage and the manual).
>
>     > Well, one other place I know where the plugged status is used is in
>     > queueing sent messages for later mass dispatch.
>
> Yeah you're right, I actually found that out when I replied to you as I
> was testing Gnus unplugged :)
> Do you know if any other backends default to being offline when
> unplugged regardless of the server being agentized?

Yes, now. Perhaps you got my follow-up mail, with this info:

  ... the ':plugged' in (info "(gnus) Mail Source Specifiers").

>     >> I think I'd find this behavior surprising (and difficult to change)
>     >> if I
>     >> encountered it as a new user, while the inconvenience of marking
>     >> every
>     >> nnatom server as agentized seems pretty minor.
>
>     > Yes, but IIUC that would make the agent store a twin copy of the
>     > headers, and every article; the latter unless maybe one fiddles with
>     > gnus-agent-eagerly-store-articles - but right now I can't set that per
>     > server.
>
> I think a better way to solve this particular issue would be to teach
> Gnus to get this information from the backend (for backends which store
> their data locally).

Yes (cf. the one case above). Though (info "(gnus) Browsing the Web")
recommends the agent.

> I wonder if the same happens with nnrss, for example.

It doesn't; OOTB anyway.

>     > Anyway it was just a thought. I'm perfectly fine with my current
>     > setup.
>
> While I have your attention, can you tell me if you encountered any bugs
> while using nnatom with the agent?
> I'm trying to fix any issues I can find with it before Emacs 30 is
> released, but as I don't use Gnus unplugged I only did some basic
> testing with it.

With my custom setup? Not really, no. But btw I did find a wanton 'cons'
in nnfeed.el#L317 while I was trying to figure that out:

  (while-let ((cg (or (and name (cons data)) ; `data' is a single group

Regards,
James