From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: non-existent gnus-topic-history
Date: Tue, 03 Jan 2012 23:54:14 +0100 [thread overview]
Message-ID: <m3ipkscs89.fsf@stories.gnus.org> (raw)
In-Reply-To: <8762ixx49e.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 06 Nov 2011 12:29:33 +0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> With an up-to-date gnus, I'm no longer able to use
> gnus-topic-move-group. It complains that `gnus-topic-history'
> (gnus-topic.el line 1306) is undefined, which it is: that's the only
> mention of that variable in the whole codebase. Simply removing that
> optional argument fixes the problem, but maybe there's a more ideal
> solution?
Fixed now.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2012-01-03 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 4:29 Eric Abrahamsen
2012-01-03 22:54 ` Lars Magne Ingebrigtsen [this message]
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=m3ipkscs89.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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).