Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: drafts/queue todays cvs -- does it work?
Date: 12 Nov 2000 20:12:17 -0500	[thread overview]
Message-ID: <2nr94gwu8e.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <m31ywgd7k4.fsf@pgnus-5.8.8-cvs.now.playing>

Harry Putnam <reader@newsguy.com> writes:

> Setting up a new machine and had occasion to download latest cvs today
> on first usages I see no messages being shown in drafts/queue although
> I've sent a few there, by sending while unplugged.  Gnus dutifully
> sends them to drafts/queue and then promptly forgets they are there.
> 
> Pressing `g' shows no messages in drafts/queue and attempting to enter
> gives the message:
> 
>   Retrieving newsgroup: nndraft:queue...
>   
>   Couldn't request group nndraft:queue: 

Do you use any nnmh server?  

Could you check the value of nnmh-directory after typing `M-g' on the
nndraft:queue?

> I did get a core dump and error 2 when compiling the new sources.
> 
> The end of `./configure && make' looked like:
> [...]
>    Wrote /usr/local/gnus/lisp/gnus-soup.elc
>    Wrote /usr/local/gnus/lisp/gnus-spec.elc
>    Wrote /usr/local/gnus/lisp/gnus-srvr.elc
>    Fatal error (11).make[1]: *** [all] Segmentation fault (core dumped)
>    make[1]: Leaving directory `/usr/local/gnus/lisp'
>    make: *** [lick] Error 2

You'd better report an Emacs bug, `M-x report-emacs-bug'.

ShengHuo



  reply	other threads:[~2000-11-13  1:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-13  0:44 Harry Putnam
2000-11-13  1:12 ` ShengHuo ZHU [this message]
2000-11-13  2:33   ` Harry Putnam
2000-11-13  3:11     ` ShengHuo ZHU

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=2nr94gwu8e.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).