unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: emacs-devel@gnu.org, Kevin Greiner <kgreiner@compsol.cc>
Subject: Re: Problem with Gnus
Date: Wed, 20 Oct 2004 18:42:07 +0200	[thread overview]
Message-ID: <v94qkpl4tc.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: E1CKILU-0000D5-P5@lists.gnu.org

[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]

On Wed, Oct 20 2004, Kim F. Storm wrote:

[ Changing the order of the questions...]
> Q2:  What about legacy-gnus-agent.el ?
>
> Looking at the code in gnus-start.el, it seems to expect
> a file named legacy-gnus-agent.el (also according to ChangeLog).
>
> Anybody else having seen this?

Yes.  After adding `legacy-gnus-agent.el' (from the current Gnus
trunk; see attachment) to emacs/lisp/gnus, it worked for me.

Kevin has synched some agent-related bugfixes from the trunk to the
v5-10 branch.  It seems he forgot to install `legacy-gnus-agent.el' in
the v5-10 branch.

In order to minimize the inconvenience, I think it's best if I "cvs
add legacy-gnus-agent.el" in Emacs soon (instead of fixing it in
Gnus/v5-10 and waiting for the semi-automatic syncing).  I have to
leave now, but I can do it in a couple of hours unless someone has a
better suggestion.

> When I do M-x gnus, it now asks me
>
>   Convert gnus from version '5.11' to '5.11' (n/y/?)
>
> Q1:  Is this to be expected?
>
> Both gnus-version and gnus-newsrc-file-version are "Gnus v5.11".

Kevin, could you check for which versions a migration in
`gnus-convert-old-newsrc' is necessary for users of Gnus v5.11?  (This
version is the same as in the v5-10 branch; (gnus-continuum-version)
gives 5.11 whereas No Gnus has 5.110003.)  A problem might be that the
version numbers are not really one-dimensional anymore in the sense of
features.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

[-- Attachment #2: legacy-gnus-agent.el --]
[-- Type: application/emacs-lisp, Size: 10863 bytes --]

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2004-10-20 16:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 15:25 Problem with Gnus Kim F. Storm
2004-10-20 16:42 ` Reiner Steib [this message]
2004-10-20 22:24   ` Kevin Greiner
2004-10-21 21:34   ` Jason Rumney
2004-10-22 16:02     ` Kevin Greiner
2004-10-22 17:04       ` Reiner Steib
2004-10-23  8:43         ` Lars Magne Ingebrigtsen
2004-10-23 13:12           ` Reiner Steib
2004-10-24 16:17             ` Kevin Greiner
2004-11-14 19:49               ` Reiner Steib
2004-11-14 19:53                 ` Lars Magne Ingebrigtsen
2004-11-14 21:06                   ` Reiner Steib

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=v94qkpl4tc.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=kgreiner@compsol.cc \
    /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.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).