From: Richmond <dnomhcir@gmx.com>
To: info-gnus-english@gnu.org
Subject: Re: gnus-kill-newsgroup error
Date: Mon, 6 Apr 2020 18:16:47 +0100 [thread overview]
Message-ID: <d7b174c0-2b94-e6ab-6aad-b8bab5e1007d@gmx.com> (raw)
In-Reply-To: <87h7xwilts.fsf@ericabrahamsen.net>
Eric Abrahamsen wrote:
> Richmond <dnomhcir@gmx.com> writes:
>
>> Eric Abrahamsen wrote:
>>> Richmond <dnomhcir@gmx.com> writes:
>>>
>>>> Eric Abrahamsen wrote:
>>>>> Richmond <dnomhcir@gmx.com> writes:
>>>>>
>>>>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>>>>
>>>>>>> Richmond <dnomhcir@gmx.com> writes:
>>>>>>>
>>>>>>>> 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?
>>>>>>> `gnus-kill-newsgroup' was removed from Gnus (or at least this Gnus
>>>>>>> change was merged into Emacs master) in 2012, so it's been a while.
>>>>>> Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
>>>>> That's a pretty old Emacs -- is there a chance you could upgrade to 26?
>>>>> 27 is almost out.
>>>> Probably but I am not sure I want to just yet. On the last system which
>>>> is now dead I did upgrade but it caused various other problems.
>>>>
>>>>>>> What version of Emacs are you using? You're not still loading an
>>>>>>> external Gnus installation, are you?
>>>>>>>
>>>>>> No. I had to re-install linux etc. So starting from scratch.
>>>>>>
>>>>>>> You talk about changes, and "reapplying changes", what does that mean?
>>>>>> Some time ago, maybe a couple of months, I asked in this group why gnus
>>>>>> was subscribing to groups and as a result of that I made changes to
>>>>>> .gnus and got rid of .gnu-emacs-custom
>>>>>>> What seems most likely is that you've got some custom functions in
>>>>>>> your.gnus.el or elsewhere that are still calling `gnus-kill-newsgroup'.
>>>>>>>
>>>>>> The problem is I cannot find any reference to it.
>>>>>>
>>>>>> I do this:
>>>>>>
>>>>>> find . -type f -print|xargs grep -i gnus-kill-newsgroup
>>>>>>
>>>>>> All it finds is this:
>>>>>>
>>>>>> ./dotgnu-emacs: (gnus-kill-newsgroup newsgroup)))
>>>>> So presumably this file is getting loaded somehow? I don't see that
>>>>> that's a standard filename of any sort. If you look at that file, what
>>>>> is that code a part of?
>>>> I don't think it is getting loaded, although it might be. But it was the
>>>> file which was called .gnu-emacs which I renamed to dotgnu-emacs so that
>>>> it wouldn't get used. (dot = . )
>>> If it's not getting loaded, I can't think of what else could be causing
>>> the problem. Unless you've got some old *elc files lying around from a
>>> previous installation. But if you're confident that you've searched all
>>> the relevant locations, I'd say this file is still your culprit.
>> I have changed the permissions on the file to zero so that it could not
>> be loaded, but I didn't get any error.
>>
>> I am not able to prove much now, one way or another, because I removed
>> and re-added the mozilla newsgroup.
>>
>> I have an idea which is pure speculation that gnus had somehow recorded
>> its intention to kill some newsgroups because that's what I had been
>> doing - killing new groups which I had been subscribed to, using ctrl-k,
>> and so gnus was trying to finish this task on startup. But I can't see
>> how this would have been recorded anywhere without recording the name
>> "gnus-kill-newsgroup", unless it was encoded.
> A completely nuts possibility is that you had a .gnus-dribble file from
> an older Emacs, which had recorded a lambda containing a call to
> `gnus-kill-newsgroup' as part of Gnus's undo mechanism as you were
> killing. I'm just totally making things up at this point. But it sounds
> like the problem is gone?
It has gone for the time being, hopefully it will not return as I have
removed the instruction to subscribe automatically to new groups.
You theory is not nuts, but wouldn't I have found the lambda with my
find command? or maybe it would be a pointer only to something which
does not now exist?
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2020-04-06 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 8:25 Richmond
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 [this message]
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=d7b174c0-2b94-e6ab-6aad-b8bab5e1007d@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).