* nnoo bug
@ 2006-02-13 7:17 Katsumi Yamaoka
2006-04-12 6:13 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 2+ messages in thread
From: Katsumi Yamaoka @ 2006-02-13 7:17 UTC (permalink / raw)
Hi,
There's a mystery of long standing that the `nndraft-directory'
variable is sometimes set to the symbol `nndraft-directory'. At
that time, the `nnmh-directory' variable is also set to the
symbol `nndraft-directory'. It might happen to only people who
are interested in debugging and developing Gnus, though. Now I
found out the way to reproduce it and the cause of the problem.
To reproduce the problem, enter the nndraft:drafts group[1],
load the nnmh library or the nndraft library, and exit the group.
The cause is that the `nnoo-declare' macro[2] adds the new entry
to the variables `nnoo-definition-alist' and `nnoo-state-alist'
whenever it is called. When the nnmh module is re-loaded in the
nndraft:drafts group, the `nnoo-declare' macro registers the
nnmh back end in the `nnoo-state-alist' variable as
"*internal-non-initialized-backend*". Because of this, the
`(nnmh-directory nndraft-directory)' element in the nndraft
entry which is registered in the `nnoo-definition-alist'
variable is processed by the `nnoo-change-server' function[3]
when exiting the nndraft:drafts group as:
(set 'nnmh-directory 'nndraft-directory)
even though it should be:
(set 'nnmh-directory (symbol-value 'nndraft-directory))
[1] It is required that there is at least one draft in the
nndraft:drafts group.
[2] All the nn* modules call the `nnoo-declare' macro at the top
level.
[3] The `nnoo-change-server' function is called by way of the
`gnus-close-server' function when exiting the nndraft group.
I've fixed the `nnoo-declare' macro so that it might never
generate duplicate entries. BTW, does anyone know the reason to
use `eval-and-compile' there? I left it.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: nnoo bug
2006-02-13 7:17 nnoo bug Katsumi Yamaoka
@ 2006-04-12 6:13 ` Lars Magne Ingebrigtsen
0 siblings, 0 replies; 2+ messages in thread
From: Lars Magne Ingebrigtsen @ 2006-04-12 6:13 UTC (permalink / raw)
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> I've fixed the `nnoo-declare' macro so that it might never
> generate duplicate entries. BTW, does anyone know the reason to
> use `eval-and-compile' there? I left it.
I seem to dimly remember I was trying lots of stuff back and forth
when doing those macros. The `eval-and-compile' may or may not be
necessary. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-04-12 6:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-02-13 7:17 nnoo bug Katsumi Yamaoka
2006-04-12 6:13 ` Lars Magne Ingebrigtsen
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).