From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: drafts/queue todays cvs -- does it work?
Date: 12 Nov 2000 22:11:14 -0500 [thread overview]
Message-ID: <2nr94gva5p.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <m3ofzkha7j.fsf@pgnus-5.8.8-cvs.now.playing>
Harry Putnam <reader@newsguy.com> writes:
[...]
> However, oddly enough the value requested shows an nnmh directory that
> is a directory where I conduct experimental work with search tools I'm
> working on. Not a message directory at all. And I'm certain I never
> created an nnmh group of any kind.
>
> `C-h v' nnmh-directory <RET>
>
> nnmh-directory's value is
> "/home/reader/projects/awk/search-work/"
Both nndir and nndraft are derived from nnmh. nnmh-directory is an
"oo" variable. "oo" variables are copied between a derived backend
and its parent backend. If your search tools are backends, you should
use nnoo-change-server and nnoo-parent-function to access the parent
backends. If you just want to set "oo" variables, you should use
nnoo-set (only valid in the recent CVS).
> > > 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'.
>
> So are you saying that the error above is not related to something in
> the latest cvs distribution?
Right.
ShengHuo
prev parent reply other threads:[~2000-11-13 3:11 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
2000-11-13 2:33 ` Harry Putnam
2000-11-13 3:11 ` ShengHuo ZHU [this message]
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=2nr94gva5p.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).