>>>> "Ilpo" == Ilpo Nyyssönen
<iny+dev(a)iki.fi> writes:
Ilpo> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
>>
>>>> "Ilpo" == Ilpo
Nyyssönen <iny+dev(a)iki.fi> writes:
Ilpo> >
Ilpo> ================================================================
Ilpo> Dear Bug Team!
Ilpo> >
Ilpo> Signaling: (wrong-type-argument window-live-p #<window 0x10fbec>)
Ilpo> select-window(#<window 0x10fbec>)
Ilpo> #<compiled-function nil "...(34)" [gnus-summary-buffer
GnusStartBufferWindow buf w selected-window gnus-get-buffer-window visible (...)
select-window window-buffer pop-to-buffer gnus-summary-next-page] 3
("/opt/xemacs/lib/xemacs/site-packages/lisp/gnus/gnus-art.elc" . 127155)
nil>()
Ilpo> call-interactively(gnus-article-goto-next-page)
Ilpo> (dispatch-event "[internal]")
Ilpo> >
> What version of Gnus is this? (I saw this problem with Oort 0.12
or
> so, but it went away somewhere between 0.13 and 0.15.)
Ilpo> CVS version, compiled at the same time the XEmacs was compiled, if I
Ilpo> recall correctly. The version number seems to be 0.16. And my Gnus
Ilpo> setup is not the standard one at all.
Ilpo> The error doesn't seem to cause any harm. If I go ahead from the last
Ilpo> article in a group to the next group, it beeps and shows the error.
Ilpo> And I use gnus-pick-mode, which causes the focus to be in the article
Ilpo> buffer. (If I go ahead from the summary buffer, the error doesn't
Ilpo> occur.)
Can you get a source-level backtrace so I can figure out which call to
`select-window' this is?
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla