Lars Ingebrigtsen <larsi@gnus.org> writes:

> Daiki Ueno <ueno@gnu.org> writes:
>
>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>
>>> Debugger entered--Lisp error: (error "Unknown service: 993")
>>>   make-network-process(:name "*nnimap*" :buffer #<buffer *nnimap nil
>>> nil *nntpd**-409419> :host nil :service "993" :nowait nil)
>>>
>>> [...]
>>>
>>>   nnimap-change-group(nil "server")
>>>
>>> Still the literal string "server", which surely has to be wrong...
>
> [...]
>
>>       gnus-secondary-select-methods
>>       '((nnimap "server"
>> 		(nnimap-address "......")
>> 		(nnir-search-engine imap))))
>
> Oh, your nnimap server is actually called "server".  :-)  Then the
>
>>>   nnimap-change-group(nil "server")
>
> part of the backtrace is as it should be.  I think.  But the right
> nnimap-address still isn't set.  Hm...

I had a bit closer look at this, comparing the backtraces taken from
24.5 (works ok) and the git master (doesn't work).

The call sequences until `nnimap-open-server' are:

24.5:
  gnus-group-get-new-news-this-group
    -> gnus-activate-group
      -> gnus-open-server
        -> nnimap-open-server

master:
  gnus-group-get-new-news-this-group
    -> gnus-request-group-scan
      -> nnimap-request-group-scan
        -> nnimap-change-group
          -> nnimap-open-server

In the former case, `nnimap-open-server' is called with an alist entry
containing `nnimap-address', etc., while in the latter case, the
function takes "server", nil, nil.

So I guess a simple work around would be to replicate the same sequence
starting from `gnus-activate-group', if server is not opened.

Does the attached patch look correct?

To be honest, this issue is no longer priority for myself, since I
changed my habit to always use M-x gnus, as nnimap is fast enough these
days :-)

Regards,
-- 
Daiki Ueno