From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "Adam Sjøgren" <asjo@koldfront.dk>
Cc: ding@gnus.org
Subject: Re: Args out of range when quitting search buffer with recent Emacs/Gnus
Date: Sun, 13 Sep 2020 14:01:42 -0700 [thread overview]
Message-ID: <87y2ldqtl5.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87mu1te75x.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Sun, 13 Sep 2020 22:46:50 +0200")
Adam Sjøgren <asjo@koldfront.dk> writes:
> Eric writes:
>
>> Grr... yes that was what I was after, but that's not helpful. Two others
>> I neglected:
>>
>> (gnus-uncompress-range
>> (gnus-info-read (gnus-get-info gnus-newsgroup-name)))
>>
>> and:
>>
>> gnus-newsgroup-articles
>
> So, I'm not quite sure to go about these, but I did:
>
> (setq asjo-gur (gnus-uncompress-range
> (gnus-info-read (gnus-get-info gnus-newsgroup-name))))
>
> and got:
>
> asjo-gur’s value is
> (1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94)
>
> so that seems to correspond nicely to the 94 articles in the search
> group.
>
> The other one looks sane to me as well:
>
> gnus-newsgroup-articles is a variable defined in ‘gnus-sum.el’.
> Its value is
> (1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94)
> Local in buffer *Summary nnselect:nnselect-87r1r5e7et.fsf*; global value is nil
>
> Documentation:
> List of articles in the current newsgroup.
Okay, thanks for that. So assuming I'm reading the code right, you don't
actually have any bum values for buffer-local mark lists. In this case I
think we might want to look at leakage in the various define-inlines. I
can't immediately see anything wrong, but maybe there's a crucial
`inline-letevals' missing somewhere. The fact that you're always hitting
this 1000 makes me think that a symbol that was meant to be locally
scoped is somehow getting set globally.
Last shot in the dark and then I'm going to pass this back to Andy: is
the plain symbol `sequence' defined globally?
next prev parent reply other threads:[~2020-09-13 21:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 18:53 Adam Sjøgren
2020-09-13 12:43 ` Andrew Cohen
2020-09-13 13:11 ` Adam Sjøgren
2020-09-13 13:53 ` Andrew Cohen
2020-09-13 14:06 ` Adam Sjøgren
2020-09-13 14:20 ` Andrew Cohen
2020-09-13 14:27 ` Adam Sjøgren
2020-09-13 15:51 ` Andrew Cohen
2020-09-13 16:13 ` Adam Sjøgren
2020-09-13 19:27 ` Eric Abrahamsen
2020-09-13 19:45 ` Adam Sjøgren
2020-09-13 20:26 ` Eric Abrahamsen
2020-09-13 20:46 ` Adam Sjøgren
2020-09-13 21:01 ` Eric Abrahamsen [this message]
2020-09-13 23:30 ` Andrew Cohen
2020-09-13 23:48 ` Andrew Cohen
2020-09-14 16:02 ` Adam Sjøgren
2020-09-14 20:28 ` Eric Abrahamsen
2020-09-14 23:27 ` Andrew Cohen
2020-09-14 15:47 ` Adam Sjøgren
2020-09-13 16:48 ` 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=87y2ldqtl5.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=asjo@koldfront.dk \
--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).