From: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: Attached pgp and mailcrypt
Date: 11 Sep 2000 18:22:43 -0700 [thread overview]
Message-ID: <m2vgw2cskc.fsf@gnus-5.8.8-cvs.now.playing> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "11 Sep 2000 23:31:21 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> On 09 Sep 2000, Harry Putnam wrote:
>
> > Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> >
> >> I have now frobbed the comments a little. What do you think?
> >
> > That proceedure doesn't do it here.
>
> Okay. Changed.
Err ... sorry but that doesn't work either. I hope its not something
in my setup causing problems but here is what I see at this end.
Placing either:
(rfc2015-setup)
*OR*
(add-hook 'gnus-startup-hook 'rfc2015-setup)
*By itself* in either .gnus or .emacs causes a function void error.
So it seems to require something else to work.
I find it needs a `require' statement to work.
Putting these at the end of gnus does the job:
(require 'rfc2015)
(add-hook 'gnus-startup-hook 'rfc2015-setup)
Proposed comment section for rfc2015.el to be included in CVS tree:
;; Installation: Put the following statements in ~/.gnus or ~/.emacs:
;; (require 'rfc2015)
;; (add-hook 'gnus-startup-hook 'rfc2015-setup)
;; You will have to make sure that the directory where this file lives
;; is mentioned in `load-path'.
I've included a backtrace after first removing the rfc2015.elc and
putting rfc2015.el in its place. Setting `(setq debug-on-error t)'
and putting (add-hook 'gnus-startup-hook 'rfc2015-setup) at the end of
.gnus (with no [(require 'rfc2015)]. Then calling gnus like this:
emacs -f gnus &
Signaling: (void-function rfc2015-setup)
rfc2015-setup()
run-hooks(gnus-startup-hook)
apply(run-hooks gnus-startup-hook)
gnus-run-hooks(gnus-startup-hook)
byte-code("\b\x0e\0 \x0e\0Æ O\0ÇÈ!É\n!\x13\f\x1e\0\r!\0Ê \x0e\x19.\0Ë ÌÍÎ\"ÏÐ\x0e\x1a\b#ÇÑ!Ò Ó\x0e\x1a!Ô ÕÖ!× ÇØ!Ð" [dont-connect did-connect gnus-startup-file gnus-current-startup-file gnus-slave gnus-use-dribble-file gnus-group-quit gnus-run-hooks gnus-startup-hook gnus-make-newsrc-file gnus-dribble-read-file bbb-login add-hook gnus-summary-mode-hook gnus-grouplens-mode gnus-setup-news nil gnus-setup-news-hook gnus-start-draft-setup gnus-group-list-groups gnus-group-first-unread-group gnus-configure-windows group gnus-group-set-mode-line gnus-started-hook gnus-use-grouplens level] 4)
gnus-1(nil nil nil)
gnus()
command-line-1(("-f" "gnus"))
command-line()
normal-top-level()
next prev parent reply other threads:[~2000-09-12 1:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2wvgqytxx.fsf@gnus-5.8.8-cvs.now.playing>
[not found] ` <vafaedl4mae.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <m2em2wook7.fsf@gnus-5.8.8-cvs.now.playing>
[not found] ` <vaf66o834w3.fsf@lucy.cs.uni-dortmund.de>
2000-09-07 12:20 ` Harry Putnam
2000-09-08 9:54 ` Kai Großjohann
2000-09-09 1:15 ` Harry Putnam
2000-09-09 9:51 ` Kai Großjohann
2000-09-09 18:51 ` Harry Putnam
2000-09-11 21:31 ` Kai Großjohann
2000-09-12 1:22 ` Harry Putnam [this message]
2000-09-12 8:39 ` Marco Lonsing
2000-09-12 11:59 ` Kai Großjohann
2000-09-12 12:25 ` Harry Putnam
2000-09-12 13:29 ` Kai Großjohann
2000-09-13 4:12 ` ShengHuo ZHU
[not found] ` <m2d7ig4dle.fsf@gnus-5.8.8-cvs.now.playing>
[not found] ` <vaf7l8oxmg5.fsf@lucy.cs.uni-dortmund.de>
2000-09-07 23:34 ` Harry Putnam
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=m2vgw2cskc.fsf@gnus-5.8.8-cvs.now.playing \
--to=reader@newsguy.com \
--cc=ding@gnus.org \
/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).