Gnus development mailing list
 help / color / mirror / Atom feed
From: Francisco Solsona <solsona@deprof.fciencias.unam.mx>
Subject: Re: Pterodactyl Gnus v0.18 is released
Date: 07 Sep 1998 22:25:47 +-500	[thread overview]
Message-ID: <m2u32j2slg.fsf@deprof.fciencias.unam.mx> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "08 Sep 1998 04:31:28 +0200"

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> Bug fixes.
> 
> Get it from <URL:http://www.gnus.org/pgnus.tar.gz> or
> "/ftp@ftp.gnus.org:/pub/emacs/gnus/".  The patch is available as
> <URL:http://www.gnus.org/patches/pgnus-0.17-0.18.diff.gz>.

	ummm it doesn't quite work for me. ;-( While compiling the new 
version, it says:

...
While compiling the end of the data in file /home/solsona/lisp/gnus/pterodactyl-gnus/lisp/mm-bodies.el:
  ** The following functions are not known to be defined:
    coding-system-get, get-charset-property,
    find-coding-systems-region 
...
While compiling rfc2047-b-encode-region in file /home/solsona/lisp/gnus/pterodactyl-gnus/lisp/rfc2047.el:
  ** base64-encode-region called with 3 arguments, but accepts only 2
While compiling the end of the data:
  ** The following functions are not known to be defined:
    coding-system-get, get-charset-property,
    find-coding-systems-region 
...

those must be MULE specific I suppose. Then, when I try to enter a
group, I receive the message:

Invalid date: 

and a backtrace shows:

Signaling: (error "Invalid date: ")
  signal(error ("Invalid date: "))
  cerror("Invalid date: %s" "")
  apply(cerror ("Invalid date: %s" ""))
  error("Invalid date: %s" "")
  date-to-time("")
  gnus-dd-mmm("")
  (format "%c%s: %-15s%c" gnus-tmp-opening-bracket (gnus-dd-mmm (mail-header-date gnus-tmp-header)) (let (...) (if ... ... val)) gnus-tmp-closing-bracket)
)
  (insert (format "%c%s: %-15s%c" gnus-tmp-opening-bracket (gnus-dd-mmm ...) (let ... ...) gnus-tmp-closing-bracket))
)
  (progn (insert (format "%c%s: %-15s%c" gnus-tmp-opening-bracket ... ... gnus-tmp-closing-bracket)) (point))
)
  (gnus-put-text-property (point) (progn (insert ...) (point)) gnus-mouse-face-prop gnus-mouse-face)
)
  (progn (insert gnus-tmp-unread gnus-tmp-replied gnus-tmp-indentation (make-string gnus-tmp-level ?\ )) (gnus-put-text-property (point) (progn ... ...) gnus-mouse-face-prop gnus-mouse-face) (insert " " gnus-tmp-subject-or-nil "\n"))
)
  eval((progn (insert gnus-tmp-unread gnus-tmp-replied gnus-tmp-indentation (make-string gnus-tmp-level ?\ )) (gnus-put-text-property (point) (progn ... ...) gnus-mouse-face-prop gnus-mouse-face) (insert " " gnus-tmp-subject-or-nil "\n")))
  gnus-summary-insert-line([0 "" "" "" "" "" 0 0 ""] 0 nil 128 t nil "" nil 1)
  gnus-update-summary-mark-positions()
  gnus-summary-mode("nnml+private:scheme")
  gnus-summary-setup-buffer("nnml+private:scheme")
  gnus-summary-read-group-1("nnml+private:scheme" nil nil nil nil nil)
  gnus-summary-read-group("nnml+private:scheme" nil nil nil nil nil nil)
  gnus-group-read-group(nil nil nil)
  gnus-topic-read-group(nil)
  call-interactively(gnus-topic-read-group)

	I'll install a MULE aware (X)Emacs to keep testing Gnus,
(un)fortunately, I have a NON-MULE-Xemacs 20.4 right now.

Anyway...hth,
Francisco
-- 
Real Users find the one combination of bizarre input values that shuts
down the system for days.


  reply	other threads:[~1998-09-07 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-08  2:31 Lars Magne Ingebrigtsen
1998-09-07 17:25 ` Francisco Solsona [this message]
1998-09-07 22:41   ` Michael Harnois
1998-09-08  5:09     ` Lars Magne Ingebrigtsen
1998-09-08  9:42   ` Lars Magne Ingebrigtsen

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=m2u32j2slg.fsf@deprof.fciencias.unam.mx \
    --to=solsona@deprof.fciencias.unam.mx \
    /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).