From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: problem with gnus-group-make-nnir-group
Date: Mon, 31 Oct 2011 13:19:20 -0400 [thread overview]
Message-ID: <87lis1t6xz.fsf@lifelogs.com> (raw)
In-Reply-To: <87ehxue23n.fsf@gnu.org>
On Sun, 30 Oct 2011 20:00:44 +0100 "Jose A. Ortega Ruiz" <jao@gnu.org> wrote:
jao> In my version of Gnus (corresponding to a recent emacs snapshot), the
jao> problem is with the body of nnir-mode, which starts as (nnir.el:1741):
jao> (defun nnir-mode ()
jao> (when (eq (car (gnus-find-method-for-group gnus-newsgroup-name)) 'nnir)
jao> (setq gnus-summary-line-format
jao> (or nnir-summary-line-format gnus-summary-line-format))
jao> (when (gnus-bound-and-true-p gnus-registry-enabled)
jao> But both `gnus-registry-enabled' *and* `gnus-bound-and-true-p' are
jao> undefined when nnir is loaded. gnus-registry.el does define the former,
jao> but not the latter function, and in my emacs session
jao> (fboundp 'gnus-bound-and-true-p) returns nil.
I don't know how that's possible. nnir.el has
(defvar gnus-registry-enabled)
and loads gnus-util.el, which defines `gnus-bound-and-true-p'. So this
problem should not happen, and does not happen on the Gnus Buildbot
either. Can you think of something that could be causing the problem
for you but not for me and the Buildbot?
Thanks
Ted
next prev parent reply other threads:[~2011-10-31 17:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 19:17 Peter Münster
2011-10-24 23:57 ` Dave Abrahams
2011-10-25 5:24 ` Peter Münster
2011-10-25 7:21 ` Dave Abrahams
2011-10-27 17:37 ` Ted Zlatanov
2011-10-30 15:59 ` Peter Münster
2011-10-30 19:00 ` Jose A. Ortega Ruiz
2011-10-31 17:19 ` Ted Zlatanov [this message]
2011-11-01 0:01 ` Jose A. Ortega Ruiz
2011-11-01 0:54 ` Ted Zlatanov
2011-11-01 1:46 ` Jose A. Ortega Ruiz
2011-11-01 13:55 ` Ted Zlatanov
2011-10-31 17:21 ` Ted Zlatanov
2011-10-31 17:38 ` Ted Zlatanov
2011-10-31 19:58 ` Peter Münster
2011-10-31 22:19 ` Ted Zlatanov
2011-10-31 23:34 ` Ted Zlatanov
2011-11-03 7:50 ` Peter Münster
2011-11-03 21:44 ` Ted Zlatanov
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=87lis1t6xz.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).