Re: Internal error: lstream not open
"Ben Wing" <ben(a)666.com> writes:
> Internal error: lstream not open, #<INTERNAL OBJECT (XEmacs
bug?) (filedesc
lstream) 0x964a700>
you can get a backtrace, right?
Here is one such:
Signaling: (internal-error "lstream not open" #<INTERNAL OBJECT (XEmacs bug?)
(filedesc lstream) 0x8ca5dd8>)
kill-buffer(#<buffer " *server news.cs.hut.fi nntp *nntpd**">)
nntp-kill-buffer(#<buffer " *server news.cs.hut.fi nntp *nntpd**">)
nntp-accept-response()
byte-code("..." [nntp-server-buffer alist entry buf process buffer
erase-buffer nntp-find-connection-buffer try nntp-try-list-active 0 t "LIST
ACTIVE" "GROUP" gnus-buffer-live-p nnheader-report nntp "Connection to
%s is closed." throw done nil mapconcat identity " " get-buffer
process-status (open run) nntp-kill-buffer process-buffer delq nntp-open-connection
"Couldn't open connection to %s" err (byte-code "*«
* Æ , -.«Ç !È
/P\"*Éa«Ê« «Ë
\n %Ê ö