Re: M-g doesn't work with gnus-no-server

[Ted Zlatanov <tzz@lifelogs.com>]

On Tue, 17 Mar 2015 18:06:09 +0900 Daiki Ueno <ueno@gnu.org> wrote: 

DU> Debugger entered--Lisp error: (error "server/993 Name or service not known")
DU>   make-network-process(:name "*nnimap*" :buffer #<buffer  *nnimap server nil  *nntpd**> :host "server" :service "993" :nowait nil)
DU>   open-network-stream("*nnimap*" #<buffer  *nnimap server nil  *nntpd**> "server" "993")
DU>   open-gnutls-stream("*nnimap*" #<buffer  *nnimap server nil  *nntpd**> "server" "993")
DU>   ...
DU>   nnimap-open-connection-1(#<buffer  *nntpd*>)
DU>   nnimap-open-connection(#<buffer  *nntpd*>)
DU>   nnimap-open-server("server" nil nil)
DU>   nnimap-change-group(nil "server")
DU>   nnimap-request-group-scan("INBOX" "server" ...)
DU>   gnus-request-group-scan("nnimap+server:INBOX" ...)
DU>   gnus-group-get-new-news-this-group(nil)
DU>   gnus-topic-get-new-news-this-topic(nil)
DU>   funcall-interactively(gnus-topic-get-new-news-this-topic nil)
DU>   call-interactively(gnus-topic-get-new-news-this-topic nil nil)
DU>   command-execute(gnus-topic-get-new-news-this-topic)

DU> Comparing the backtrace with the one taken with M-x debug-on-entry
DU> open-network-stream on Emacs 24.4, the DEFS argument of
DU> `nnimap-open-server' is not given on the first connection.

No idea, but can you bisect the issue to a specific commit?  That would
answer it most clearly.

Ted