From: James Thomas <jimjoe@gmx.net>
To: Dilip <idlip@protonmail.com>
Cc: ding@gnus.org
Subject: Re: How to maintain newsrc.eld clean and tidy
Date: Sat, 02 Nov 2024 06:23:51 +0530 [thread overview]
Message-ID: <861pzu317k.fsf@gmx.net> (raw)
In-Reply-To: <87o736lnnb.fsf@protonmail.com> (Dilip's message of "Sat, 26 Oct 2024 18:33:48 +0000")
Dilip wrote:
> The following message is a courtesy copy of an article
> that has been posted to gmane.emacs.gnus.general as well.
>
> Hi gnus!
>
> Gnus saves the state of reading into ~gnus-newsrc-alist~ as in elisp
> data form.
>
> When I read all messages from a group, I would expect the data form to
> shrink or minimize, but I still see long form of data for that group.
> Note: By read everything, for old messages I run
> ~gnus-topic-catchup-articles~ (=c=) on group buffer
>
> Eg:
>
> #+begin_src emacs-lisp
> (setq gnus-newsrc-alist
> '( ("nntp+news.gmane.io:gmane.comp.gnu.guix.user" 3 ((1 . 18968))
> ((unexist) (seen (1 . 18968))) "nntp:news.gmane.io") ))
> #+end_src
>
> ^ I'd expect this form to show that all have been read from 1-18968.
>
> But actually it saves data in session wise based on what were read.
>
> #+begin_src emacs-lisp
> (setq gnus-newsrc-alist
> '( ("nntp+news.gmane.io:gmane.comp.gnu.guix.user" 3 ((1 . 18968))
> ((unexist) (seen (18957 . 18968) (18937 . 18944) (18912 . 18920) ........)) "nntp:news.gmane.io") ))
> #+end_src
>
> ^ But it looks this way. Which create very long lines.
>
> May I know the significance of this form? Why can't it be simple?
>
> After searching up a bit, I notice that =gnus-topic-alist= and
> =gnus-topic-topology= and be easily maintained manually by config.
>
> So may I get some tips to maintain newsrc file clean and in version
> control. As I do want to sync with phone (android emacs app) to read
> as well.
> Basically I'm expecting to want that =gnus-newsrc-alist= (hash-table)
> to be simple in a way that only reports
>
> #+begin_src text
> ("news...." 3 ((1 . 100)) ((unexist) (seen (1 . 10))))
> #+end_src
>
> and not splits of =(1 . 2) (3 . 4) (5 . 10)= for very long lines.
Simple: add a -request-compact-group back-end function for nntp. :-)
> Thank you for taking time to read this.
No problem.
Regards,
James
next prev parent reply other threads:[~2024-11-02 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 18:33 Dilip
2024-10-26 19:48 ` Bob Newell
2024-10-26 20:54 ` Björn Bidar
[not found] ` <4904.38762806065$1729976159@news.gmane.org>
2024-10-27 5:38 ` Dilip
2024-10-27 9:51 ` Andreas Schwab
[not found] ` <87plnlr95i.fsf@protonmail.com>
2024-10-27 13:43 ` Andreas Schwab
2024-10-28 13:20 ` Björn Bidar
2024-11-02 0:53 ` James Thomas [this message]
2024-11-03 7:56 ` Dilip
2024-10-28 14:41 Dilip
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=861pzu317k.fsf@gmx.net \
--to=jimjoe@gmx.net \
--cc=ding@gnus.org \
--cc=idlip@protonmail.com \
/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).