Upgrading to Oort?

Upgrading to Oort?

[Peter Davis]

On another topic, Ichimusai <ichi@ichimusai.org> writes:

[...]

> It seems there are more and more reasons to upgrade to Oort... but
> perhaps it is possible to get html2text.el to work in my old Gnus as
> well until I get time to read up and upgrade?
> 
> I am hesitant to do it right now because I have a rather extensive
> .gnus and I'd like to know how to make the transition as smoothly as
> possible, thus I need to read up on Oort a bit before I try to
> upgrade.

This raises an interesting question:  How *do* you upgrade to Oort?  I
managed to find a 0.7 installed (via Google ... no hints in gnus.org),
but the documentation I found appears to be just the general gnus
documentation.  Is there a "differences" document discussing what a
gnus 5.8.8 or 5.9 users must to do upgrade to Oort?

Better handling of HTML seems pretty compelling, since I haven't found
any approach I'm satisfied with in gnus 5.x.

Thanks,

-pd


-- 
--------
                             Peter Davis
               Funny stuff at http://www.pfdstudio.com
                 The artwork formerly shown as prints
    List of resources for children's writers and illustrators at:
                  http://www.pfdstudio.com/cwrl.html

Re: Upgrading to Oort?

[Jesper Harder]

Peter Davis <pd@world.std.com> writes:

> This raises an interesting question: How *do* you upgrade to Oort?

Get a nightly snapshot or pull it from CVS as described on 

    <http://gnus.org/distribution.html>

Do 

     ./configure; make

and then either 'make install' or add the gnus dir to you load-path and
the texi subdir to Info-default-directory-list.

> Is there a "differences" document discussing what a gnus 5.8.8 or 5.9
> users must to do upgrade to Oort?

Look for the file GNUS-NEWS in the distribution.

Re: Upgrading to Oort?

[pd]

[-- 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)

Re: Upgrading to Oort?

[pd]

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


Well, it appears that the error I'm getting:

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

is *not* related to my code to customize the summary line.  I commented all
that out, and I'm still getting the error when I try to run gnus.  This is
under XEmacs 21.1.8 on Windows NT4.

Ideas?

Thanks,

-pd


"pd" <pd@world.std.com> wrote in message
news:vLcc9.71082$kp.725497@rwcrnsc52.ops.asp.att.net...
>
> "lawrence mitchell" <wence@gmx.li> wrote in message
> news:wkptw0ngzl.fsf@ID-97657.usr.dfncis.de...
> > pd wrote:
> >
> > [...] 5.8.x --> Oort

    [ ... ]

> > > 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 "Ä BÅÆ 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)
>
>
>
>

Re: Upgrading to Oort?

[Simon Josefsson]

"Peter Davis" <pdavis@pageflexinc.com> writes:

> Well, I thought I had Oort gnus 0.07 running.  I can read and reply to
> e-mail, and read news articles.  However, when I try to follow-up to news
> articles, I get:
>
> Searching for program: no such file or directory, openssl
>
> Any clues?

Do M-x toggle-debug-on-error RET before following up th news, and post
the backtrace you get.

> By the way, does this mean gnus now has built-in ssl support, so I can stop
> running stunnel?

The ssl support in gnus uses openssl or starttls.  I don't think there
is much improvement in changing from stunnel, if you are happy with
your current setup.

Re: Upgrading to Oort?

[Simon Josefsson]

"Peter Davis" <pdavis@pageflexinc.com> writes:

> Here's the backtrace.  I apologize for posting with OE.  As I said, I can't
> post with gnus at the moment.
>
> Signaling: (file-error "Searching for program" "No such file or directory"
> "openssl")
>   start-process-internal("*call-process*" #<buffer " *sha1 external*">
> "openssl" "sha1")

Try this patch.  It is added to CVS.

Index: message.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/message.el,v
retrieving revision 6.248
diff -u -p -u -w -r6.248 message.el
--- message.el	2002/08/28 11:24:32	6.248
+++ message.el	2002/09/04 00:52:08
@@ -3139,10 +3139,11 @@ documentation for the function `mail-sou
 (defun message-canlock-generate ()
   "Return a string that is non-trival to guess.
 Do not use this for anything important, it is cryptographically weak."
+  (let (sha1-maximum-internal-length)
   (sha1 (concat (message-unique-id)
 		(format "%x%x%x" (random) (random t) (random))
 		(prin1-to-string (recent-keys))
-		(prin1-to-string (garbage-collect)))))
+		  (prin1-to-string (garbage-collect))))))
 
 (defun message-canlock-password ()
   "The password used by message for cancel locks.

Re: Upgrading to Oort?

[Stephen J. Turnbull]

>>>>> "Peter" == Peter Davis <pdavis@pageflexinc.com> writes:

    Peter> "Stephen J. Turnbull" <stephen@xemacs.org> wrote in message
    Peter> news:87r8g37rz3.fsf@tleepslib.sk.tsukuba.ac.jp...

    >> Moral: if a package provides a Makefile, _always_ use it to
    >> build the package.

    Peter> Unless you're on Windows, where the makefiles may not work,
    Peter> and need to be simulated by hand.

AFAIK GNU Make is one of the Cygwin utilities that invariably works as
advertised (unlike FTP :-( ).

FWIW.


-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
 My nostalgia for Icon makes me forget about any of the bad things.  I don't
have much nostalgia for Perl, so its faults I remember.  Scott Gilbert c.l.py

Re: Upgrading to Oort?

[Simon Josefsson]

"Peter Davis" <pdavis@pageflexinc.com> writes:

>> Moral: if a package provides a Makefile, _always_ use it to build the
>> package.
>
> Unless you're on Windows, where the makefiles may not work, and need to be
> simulated by hand.

There should be a BAT file for compilation under windows.