Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Daiki Ueno <ueno@gnu.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,  ding@gnus.org
Subject: Re: M-g doesn't work with gnus-no-server
Date: Wed, 10 Feb 2016 10:34:57 +1100	[thread overview]
Message-ID: <87a8n9790e.fsf@gnus.org> (raw)
In-Reply-To: <m3egcml1f6.fsf-ueno@gnu.org> (Daiki Ueno's message of "Tue, 09 Feb 2016 17:42:53 +0900")

Daiki Ueno <ueno@gnu.org> writes:

> 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

[...]

> * lisp/gnus/gnus-group.el: Don't call `gnus-request-group-scan' if
> server is not opened.

Well, we want `M-g' to open the server if it isn't already...  so
perhaps we should just call `gnus-activate-group'?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2016-02-09 23:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17  9:06 Daiki Ueno
2015-04-17 20:00 ` Ted Zlatanov
2016-02-07  3:02 ` Lars Ingebrigtsen
2016-02-07  8:54   ` Andreas Schwab
2016-02-07  9:26   ` Andreas Schwab
2016-02-07 12:32   ` Andreas Schwab
2016-02-07 18:03     ` Daiki Ueno
2016-02-07 18:27       ` Dave Goldberg
2016-02-08  5:10       ` Lars Ingebrigtsen
2016-02-08  5:47         ` Daiki Ueno
2016-02-08  5:54           ` Lars Ingebrigtsen
2016-02-09  8:42             ` Daiki Ueno
2016-02-09 23:34               ` Lars Ingebrigtsen [this message]
2016-02-10  4:20                 ` Daiki Ueno
2016-02-12 10:47                   ` Andreas Schwab
2016-02-13  6:43                   ` Lars Ingebrigtsen
2016-02-13  7:21                     ` Daiki Ueno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a8n9790e.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=schwab@linux-m68k.org \
    --cc=ueno@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).