Gnus development mailing list
 help / color / mirror / Atom feed
From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: ding@gnus.org
Subject: Re: problem with gnus-group-make-nnir-group
Date: Tue, 01 Nov 2011 01:01:41 +0100	[thread overview]
Message-ID: <8762j4d8wr.fsf@gnu.org> (raw)
In-Reply-To: <87lis1t6xz.fsf@lifelogs.com>


Hi Ted,

On Mon, Oct 31 2011, Ted Zlatanov wrote:


[...]

> jao> But both `gnus-registry-enabled' *and* `gnus-bound-and-true-p'
> jao> are undefined when nnir is loaded.  gnus-registry.el does define
> jao> the former, 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)

The variable is declared, but still unbound: trying to use it will raise
an error (because it has no value).

> and loads gnus-util.el, which defines `gnus-bound-and-true-p'.

This is a macro defined inside an eval-when-compile: the packaged Emacs
comes with a compiled version (gnus-util.elc), and it's the compiled
file that gets loaded when (require 'gnus-util) is called.  The idiom of
wrapping macros in an eval-when-compile form is intended for macros that
are going to be used in the same file that defines them.

> 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?

Unless i'm missing something, the only explanation i have is that you're
loading source elisp files instead of compiled byte code.  Could that be
the case?

Cheers,
jao
-- 
"People sometimes ask me if it is a sin in the Church of Emacs to use vi.
 Using a free version of vi is not a sin; it's a penance".
  -Richard Stallman




  reply	other threads:[~2011-11-01  0:01 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
2011-11-01  0:01               ` Jose A. Ortega Ruiz [this message]
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=8762j4d8wr.fsf@gnu.org \
    --to=jao@gnu.org \
    --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).