Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "pd" <pd@world.std.com>
Subject: Re: Upgrading to Oort?
Date: Sat, 31 Aug 2002 23:59:23 GMT	[thread overview]
Message-ID: <vLcc9.71082$kp.725497@rwcrnsc52.ops.asp.att.net> (raw)
In-Reply-To: <wkptw0ngzl.fsf@ID-97657.usr.dfncis.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3495 bytes --]


"lawrence mitchell" <wence@gmx.li> wrote in message
news:wkptw0ngzl.fsf@ID-97657.usr.dfncis.de...
> pd wrote:
>
> [...] 5.8.x --> Oort
>
> > 1) I'd like to know how Oort differs from 5.x, so I can estimate how
much
> > work it will take to modify my .gnus file, etc.  I gather that some
changes
> > are required, at least if I want to take advantage of the new features
of
> > Oort.
>
> Bug reports of things failing to work are always useful, since
> then, the developers can make sure that they won't fail once Oort
> is released.

Will do.

> > 2) I'm caught in a Windows world, so configure, etc. don't work for me.
>
> No problem, the gnus distribution comes with a make.bat, which
> may do what you need.  However, you most likely only really want
> to compile the gnus files:

<stuff deleted>

I did add the path, and compile the .el files.  I haven't worried about the
info files yet because trying to load infohack didn't work for me (with
XEmacs 21.1.8).

However, when I tried to run gnus, I got:

Wrong number of arguments: gnus-continuum-version, 0

The traceback looks like this:

Signaling: (wrong-number-of-arguments gnus-continuum-version 0)
  gnus-continuum-version()
  byte-code("..." [gnus-summary-line-format-spec
gnus-summary-dummy-line-format-spec gnus-group-line-format-spec
emacs-version version gnus-version gnus-continuum-version group
"%M%S%p%P%5y: %(%g%)%l\n" summary-dummy "*  %(:                          :%)
%S\n" summary "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n"] 7)
  (defvar gnus-format-specs (byte-code "Ä\vBÅÆ BÇÈ\nEÉÊ EËÌ\bE¯\x05?"
[gnus-summary-line-format-spec gnus-summary-dummy-line-format-spec
gnus-group-line-format-spec emacs-version version gnus-version
gnus-continuum-version group "%M%S%p%P%5y: %(%g%)%l\n" summary-dummy "*  %(:
:%) %S\n" summary "%U%R%z%I%(%[%4L: %-23,23f%]%) %s\n"] 7) ("d:\\Program
Files\\XEmacs\\xemacs-packages\\ognus-0.07\\lisp\\gnus-spec.elc" . 2590))
  load-internal("gnus-spec" nil t nil binary)
  load("gnus-spec" nil t nil)
  require(gnus-spec)
  byte-code("..." [require gnus gnus-win gnus-int gnus-spec gnus-range
gnus-util message] 2)
  load-internal("gnus-start" nil nil nil binary)
  load("gnus-start" nil nil nil)
  gnus-1(nil nil nil)
  gnus(nil)
  call-interactively(gnus)
  command-execute(gnus t)
  execute-extended-command(nil)
  call-interactively(execute-extended-command)

Looks like it has something to do with my attempt to customize the summary
line, which is like this:

(setq gnus-summary-line-format "%U%R%z%I%(%[%4L: %-20,20n%]%) %d %(%s%)\n")
(setq gnus-group-line-format "%M%S%p%P%3y: %(%g%)%l %uA\n")

(defun gnus-user-format-function-A (header)
  (if (string-match "nnml:\\(.*\\)" gnus-tmp-group)
      (let ((directory (nnmail-group-pathname
                        (match-string 1 gnus-tmp-group)
                        "D:\\home\\mail")))
        (concat "(" (int-to-string
                     ( - (length (directory-files directory)) 3))
                                        ; . .. .overview
                ")"))
    ""))

;; From: Colin Walters <walters@cis.ohio-state.edu>
(defun pd/gnus-set-summary-line-format ()
  (interactive)
  (setq gnus-summary-line-format
        (cond ((string-match "todo" gnus-newsgroup-name)
               "todo: %d: %S\n")
              ((string-match "notes" gnus-newsgroup-name)
               "Note: %d: %S\n")
              (t
               "%U%R%z%I%(%[%4L: %-20,20n%]%) %d %s\n"))))

(add-hook 'gnus-summary-mode-hook 'pd/gnus-set-summary-line-format)


  parent reply	other threads:[~2002-08-31 23:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-30 14:08 Peter Davis
2002-08-30 15:22 ` Jesper Harder
     [not found] ` <WhRb9.60032$_91.1666@rwcrnsc51.ops.asp.att.net>
     [not found]   ` <wkptw0ngzl.fsf@ID-97657.usr.dfncis.de>
2002-08-31 23:59     ` pd [this message]
2002-09-01  0:30       ` pd
     [not found]         ` <fzwurrzm.fsf@hschmi22.userfqdn.rz-online.de>
     [not found]           ` <fZyc9.95522$_91.105431@rwcrnsc51.ops.asp.att.net>
     [not found]             ` <iluwuq5c9iq.fsf@latte.josefsson.org>
     [not found]               ` <6PLc9.90671$kp.732844@rwcrnsc52.ops.asp.att.net>
     [not found]                 ` <SVLc9.90789$kp.733254@rwcrnsc52.ops.asp.att.net>
     [not found]                   ` <al2gn8$umi$1@news.bitstream.com>
2002-09-03 16:34                     ` Simon Josefsson
     [not found]                       ` <al2sbo$vbs$1@news.bitstream.com>
2002-09-04  0:20                         ` Simon Josefsson
     [not found]                   ` <87r8g37rz3.fsf@tleepslib.sk.tsukuba.ac.jp>
     [not found]                     ` <ali76b$a9u$1@news.bitstream.com>
2002-09-10 13:38                       ` Stephen J. Turnbull
2002-09-11  7:40                       ` Simon Josefsson

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='vLcc9.71082$kp.725497@rwcrnsc52.ops.asp.att.net' \
    --to=pd@world.std.com \
    /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).