From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 35130@debbugs.gnu.org, James Cloos <cloos@jhcloos.com>
Subject: bug#35130: 27.0.50; gnus cannot save
Date: Wed, 03 Apr 2019 15:43:19 -0700 [thread overview]
Message-ID: <871s2iu2uw.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87r2aipxgj.fsf@tcd.ie> (Basil L. Contovounesios's message of "Wed, 03 Apr 2019 22:53:32 +0100")
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
> James Cloos <cloos@jhcloos.com> writes:
>
>> As of master commit 39c0795ef2d592d4632516ee57f1cf51a2159608 gnus is
>> unable to save.
>>
>> The error (w/ debug-on-error t) is:
>>
>> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>> gnus-gnus-to-newsrc-format()
>> gnus-save-newsrc-file(nil)
>> gnus-group-save-newsrc(nil)
>> funcall-interactively(gnus-group-save-newsrc nil)
>> call-interactively(gnus-group-save-newsrc nil nil)
>> command-execute(gnus-group-save-newsrc)
>>
>> I also got that error a few times while trying to sort the *Group*
>> buffer, but then that started working.
>>
>> Saving has not started working.
>>
>> At a quick look of the recent history, commits
>> a09306d53ba86b4596219b2be723659f7c0f2669 and
>> a8efdd4c62fbf9c275a57f71cc8a3ca845ad3b1f look relevant.
>
> Could this be related to bug#34983?
> Does the error still occur after a 'make bootstrap'?
>
> https://debbugs.gnu.org/34983
This sounds more similar to something that Bastien Guerry reported -- I
think it's all part of the same basic error, but probably won't be
solved by a "make bootstrap" (though it can't hurt to try)...
Eric
next prev parent reply other threads:[~2019-04-03 22:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 21:07 bug#35130: 27.0.50; gnus cannot save James Cloos
2019-04-03 21:53 ` Basil L. Contovounesios
2019-04-03 22:43 ` Eric Abrahamsen [this message]
2019-04-04 21:19 ` James Cloos
2019-04-09 18:56 ` Eric Abrahamsen
2019-04-10 11:00 ` James Cloos
2019-04-14 4:42 ` James Cloos
2019-04-21 17:53 ` Eric Abrahamsen
2019-04-22 13:11 ` James Cloos
2019-04-30 18:32 ` James Cloos
2019-04-30 21:19 ` Eric Abrahamsen
2019-04-30 22:54 ` James Cloos
2019-04-30 23:25 ` Eric Abrahamsen
2019-05-01 14:58 ` James Cloos
2019-05-03 19:58 ` Eric Abrahamsen
2019-06-22 12:46 ` Lars Ingebrigtsen
2019-09-27 15:00 ` Lars Ingebrigtsen
2019-04-30 21:23 ` James Cloos
2019-04-30 21:34 ` Eric Abrahamsen
2019-04-30 22:55 ` James Cloos
2019-04-30 23:18 ` Eric Abrahamsen
2019-04-30 23:52 ` Basil L. Contovounesios
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=871s2iu2uw.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=35130@debbugs.gnu.org \
--cc=cloos@jhcloos.com \
--cc=contovob@tcd.ie \
/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).