Gnus development mailing list
 help / color / mirror / Atom feed
From: Thomas Skogestad <tskogest@jusstud.uio.no>
Subject: CVS: Symbol's function definition is void: ignore-errors
Date: 04 Dec 1999 12:42:11 +0100	[thread overview]
Message-ID: <3153296531820047@birk150.studby.uio.no> (raw)

I've never tried CVS before, but I followed the instructions at 
http://www.gnus.org/distribution.html.

(cvs -v gives Concurrent Versions System (CVS) 1.10.6 (client/server))

After downloading (or whatever it's called), I tried starting with
the CVS-Gnus, however just after Gnus has started loading I get the
following error message: Symbol's function definition is void:
ignore-errors  

Just what version is supposed to be downloaded? (gnus.el claims to be
5.8.3)

(Things work just fine with 5.8.2 downloaded from the ftp site.)

If it's of any interest, the debug trace is:

Signaling: (void-function ignore-errors)
  (ignore-errors (nconc (list ... ...) (if ... nil ...)))
  eval((ignore-errors (nconc (list ... ...) (if ... nil ...))))
  custom-initialize-reset(gnus-select-method (ignore-errors (nconc (list ... ...) (if ... nil ...))))
  custom-declare-variable(gnus-select-method (ignore-errors (nconc (list ... ...) (if ... nil ...))) ("/home/thomas/gnus/gnus-5.8.cvs/lisp/gnus.elc" . -20416) :group gnus-server :type gnus-select-method)
  gnus()
  command-line-1(("-f" "gnus"))
  command-line()
  normal-top-level()

-- 
thomas.skogestad@jusstud.uio.no * http://www.ntnu.no/y2k/
http://www.rock103.com/crew/pics/promnight.jpg
http://cgi.mercurycenter.com/premium/comics/10_13/dilbert.gif
http://cgi.mercurycenter.com/premium/comics/11_19/bizarro.gif


             reply	other threads:[~1999-12-04 11:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-04 11:42 Thomas Skogestad [this message]
1999-12-04 13:11 ` Raymond Scholz
1999-12-04 16:51   ` Andi Hechtbauer
1999-12-04 16:52 ` Michael Welsh Duggan
1999-12-04 17:00   ` Andi Hechtbauer
1999-12-04 17:11     ` Shenghuo ZHU
1999-12-04 17:45       ` Per Abrahamsen
1999-12-07  4:39         ` Emerick Rogul
1999-12-07 10:43           ` Per Abrahamsen
1999-12-07 12:19           ` Thomas Skogestad
1999-12-07 12:46             ` Per Abrahamsen
1999-12-07 14:22               ` Raymond Scholz
1999-12-07 14:38                 ` Per Abrahamsen
1999-12-07 16:07                   ` Emerick Rogul
1999-12-07 14:51           ` Dave Love
1999-12-04 17:11     ` Michael Welsh Duggan
1999-12-04 17:57 ` Dave Love
1999-12-04 18:21   ` Hrvoje Niksic
1999-12-04 19:31     ` Lars Magne Ingebrigtsen
1999-12-04 19:42       ` Lars Magne Ingebrigtsen
1999-12-06 14:03         ` Andreas Schwab
1999-12-04 19:44       ` Hrvoje Niksic
1999-12-04 19:58         ` Lars Magne Ingebrigtsen
1999-12-04 20:10           ` Hrvoje Niksic
1999-12-04 20:36             ` Lars Magne Ingebrigtsen
1999-12-04 20:53               ` Hrvoje Niksic
1999-12-05 23:11           ` Kai Großjohann
1999-12-05  0:11         ` Dave Love
1999-12-05  0:06     ` Dave Love
1999-12-07 23:42     ` Eric Marsden
1999-12-07 23:50       ` David Maslen
1999-12-08  9:23       ` Hrvoje Niksic

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=3153296531820047@birk150.studby.uio.no \
    --to=tskogest@jusstud.uio.no \
    /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).