From: Ulf Stegemann <ulf-news@zeitform.de>
To: emacs-orgmode@gnu.org
Subject: Re: Problem with org-gnus-follow-link
Date: Thu, 11 Dec 2008 17:18:06 +0100 [thread overview]
Message-ID: <zf.upnk5a63cu9.fsf@zeitform.de> (raw)
In-Reply-To: 87abb2aeoh.fsf@thinkpad.tsdh.de
Hi Tassilo,
Tassilo Horn <tassilo@member.fsf.org> wrote:
> Ulf Stegemann <ulf-news@zeitform.de> writes:
>
>>> Please do a test for me:
>>>
>>> 1. Enter a group in Gnus
>>> 2. Delete the last article
>>> 3. Exit summary
>>> 4. Try `C-u 1 RET' on the group. It should issue "No unread news".
>>> 5. Do `M-: (gnus-activate-group "<group-name>" t) RET'
>>> 6. Try `C-u 1 RET' on the group again. Now it should be opened and
>>> summary should contain one article.
>>>
>>> If you get different results it seems to be due to your gnus version.
>>> I use the one included in emacs 23 and update daily, so it might be
>>> more up to date than your copy. Maybe try to update yours, too.
>>
>> done that. I was under the wrong impression that the CVS on
>> cvs.gnus.org holds the latest version of Gnus but it seems it just has
>> the release from 1st May. It seems that latest Gnus is now available
>> from the Emacs CVS only (sorry for my ignorance).
>
> There's nothing to excuse. I wasn't aware that the versions diverged
> that much, too.
yes, I really was surprised ... especially as gnus.org offers a 'nightly
snapshot' that also seems to be the version as of 1st May.
>> I installed that version here (5.13 as of today, see User-Agent
>> header)
>
> How? Did you checkout GNU Emacs and copy all the gnus-related files
> somewhere?
Exactly, I got emacs sources by CVS and used the lisp/gnus/ files (plus
some other lisp files from gnus.org that where missing and XEmacs seems
to require). Byte-Compiling here with XEmacs 21.4 went smoothly, Gnus
runs as before ... at least until now ;)
>> but again the summary buffer is not opened.
>
> That's really strange. BTW: What backend did you use for testing? I
> used nnimap. MAybe that makes the difference...
Gotcha! It works on nnimap but not on nnml which I was using for the
tests. Maybe you'll try this with your installation as well. If it fails
for nnml groups for you, too, that might be an important point for the
discussion you've started on emacs.gnus.general.
Ulf
next prev parent reply other threads:[~2008-12-11 16:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 12:24 Problem with org-gnus-follow-link Ulf Stegemann
2008-12-09 16:58 ` Tassilo Horn
2008-12-10 10:08 ` Ulf Stegemann
2008-12-10 19:08 ` Tassilo Horn
2008-12-11 10:09 ` Ulf Stegemann
2008-12-11 11:02 ` Tassilo Horn
2008-12-11 13:52 ` Ulf Stegemann
2008-12-11 14:16 ` Tassilo Horn
2008-12-11 15:37 ` Ulf Stegemann
2008-12-11 15:56 ` Tassilo Horn
2008-12-11 16:18 ` Ulf Stegemann [this message]
2008-12-11 16:41 ` Tassilo Horn
2008-12-11 18:17 ` Tassilo Horn
2008-12-11 21:51 ` Ulf Stegemann
2008-12-12 7:04 ` Tassilo Horn
2008-12-12 8:17 ` Ulf Stegemann
2008-12-12 10:31 ` Tassilo Horn
2008-12-12 14:21 ` Ulf Stegemann
2008-12-11 8:15 ` Tassilo Horn
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=zf.upnk5a63cu9.fsf@zeitform.de \
--to=ulf-news@zeitform.de \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).