From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ulf Stegemann Subject: Re: Problem with org-gnus-follow-link Date: Thu, 11 Dec 2008 11:09:08 +0100 Message-ID: References: <8763lt8euq.fsf@thinkpad.tsdh.de> <87oczjg85v.fsf@thinkpad.tsdh.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LAiTy-0002Fe-54 for emacs-orgmode@gnu.org; Thu, 11 Dec 2008 05:09:22 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LAiTx-0002F7-4X for emacs-orgmode@gnu.org; Thu, 11 Dec 2008 05:09:21 -0500 Received: from [199.232.76.173] (port=49453 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LAiTw-0002Es-RF for emacs-orgmode@gnu.org; Thu, 11 Dec 2008 05:09:20 -0500 Received: from main.gmane.org ([80.91.229.2]:48865 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LAiTw-0000Tc-F8 for emacs-orgmode@gnu.org; Thu, 11 Dec 2008 05:09:20 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LAiTs-00066M-Bd for emacs-orgmode@gnu.org; Thu, 11 Dec 2008 10:09:16 +0000 Received: from london.zeitform.net ([146.140.213.100]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Dec 2008 10:09:16 +0000 Received: from ulf-news by london.zeitform.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Dec 2008 10:09:16 +0000 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi Tassilo, Tassilo Horn wrote: > Ulf Stegemann writes: > >> this works in principle but is not really an option. Since first >> argument 't' to `gnus-group-read-group' makes every article readable >> in a group, building the summary buffer takes far too long for groups >> with many articles. Try it with groups containing 10.000+ articles and >> you'll see what I mean. > > Normally you should be asked how many articles you wanna see, if the > group is big. If that's not the case for you, you have customized > something which controls that. hmmm, I'm not aware I've ever done something like that but since my Gnus config evolved over several years I cannot completely exclude this possibility. I know the behaviour you've mentioned from nntp groups, maybe it's different with the nnml backend (I was actually testing this with nnml). > But indeed, it doesn't solve the real problem. Even if it asks and the > user says 100 but deleted the last 100 messages in that group before, > it'll react as it is now. D'accord. Tassilo Horn wrote: > please try this one: > > diff --git a/lisp/org-gnus.el b/lisp/org-gnus.el > index 7231538..05bed5b 100644 > --- a/lisp/org-gnus.el > +++ b/lisp/org-gnus.el > @@ -157,12 +157,9 @@ If `org-store-link' was called with a prefix arg the meaning of > (funcall (cdr (assq 'gnus org-link-frame-setup))) > (if gnus-other-frame-object (select-frame gnus-other-frame-object)) > (cond ((and group article) > + (gnus-activate-group group t) > (gnus-group-read-group 1 nil group) > - (gnus-summary-goto-article > - (if (string-match "[^0-9]" article) > - article > - (string-to-number article)) > - nil t)) > + (gnus-summary-goto-article article nil t)) > (group (gnus-group-jump-to-group group)))) > > (defun org-gnus-no-new-news () Unfortunately, it doesn't work. The behaviour is the same as with the original version: jumping to the article works if the last article in the group in question hasn't been deleted, otherwise it fails. Ulf