From: Richmond <dnomhcir@gmx.com>
To: info-gnus-english@gnu.org
Subject: gnus-kill-newsgroup error
Date: Sun, 05 Apr 2020 09:25:59 +0100 [thread overview]
Message-ID: <86blo672zs.fsf@gmx.com> (raw)
Due to my computer dying I lost some changes. One of which was to stop
subscribing to new groups. But even though I reapplied this change, I
was unable to launch gnus because of this error. I cannot find any
reference in the lisp to this function gnus-kill-newsgroup but something
is calling it and then failing. I got gnus working in the end by
removing the mozilla server from .gnus.
There was a reference in to this function in .gnu-emacs but I renamed
this file to dotgnu-emacs but still the error occured. Can functions get
copied around?
Debugger entered--Lisp error: (void-function gnus-kill-newsgroup)
(gnus-kill-newsgroup newsgroup)
(lambda (newsgroup) (gnus-subscribe-newsgroup newsgroup) (gnus-kill-newsgroup newsgroup))("nntp+news.mozilla.org:mozilla.dev.l10n.ta")
gnus-call-subscribe-functions((lambda (newsgroup) (gnus-subscribe-newsgroup newsgroup) (gnus-kill-newsgroup newsgroup)) "nntp+news.mozilla.org:\
mozilla.dev.l10n.ta")
[*******deleted stuff here which contained a long list of groups and control characters]
gnus-1(nil nil nil)
gnus(nil)
funcall-interactively(gnus nil)
call-interactively(gnus record nil)
command-execute(gnus record)
execute-extended-command(nil "gnus" "gnus")
funcall-interactively(execute-extended-command nil "gnus" "gnus")
call-interactively(execute-extended-command nil nil)
command-execute(execute-extended-command)
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next reply other threads:[~2020-04-05 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 8:25 Richmond [this message]
2020-04-05 15:25 ` Eric Abrahamsen
2020-04-05 17:53 ` Richmond
2020-04-06 15:53 ` Eric Abrahamsen
2020-04-06 16:04 ` Richmond
2020-04-06 16:19 ` Eric Abrahamsen
2020-04-06 16:55 ` Richmond
2020-04-06 17:08 ` Eric Abrahamsen
2020-04-06 17:16 ` Richmond
2020-04-06 17:33 ` 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=86blo672zs.fsf@gmx.com \
--to=dnomhcir@gmx.com \
--cc=info-gnus-english@gnu.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).