From: Gerald <gutier@intergate.bc.ca>
Cc: gutier@intergate.bc.ca
Subject: GNUS/Decoding & be-dangerous problem!
Date: Mon, 21 Jun 1999 23:26:02 -0700 (PDT) [thread overview]
Message-ID: <14191.11006.890236.809580@localhost> (raw)
Hi all.
I've been trying to set up the XEmacs gnus so that I can decode
messages automatically without user intervention. If the decoder tries
to decode a file that already exists, just overwrite it. Continue
without exception.
To that end, I've got the following set up in my .emacs:
(require 'gnus-uu)
(setq gnus-uu-be-dangerous 't)
(setq gnus-uu-grabbed-file-functions 'gnus-uu-grab-move)
What I've read in the documentation is that setting be-dangerous to
true means that the decoder will overwrite anything. However, it's not
doing this. When I mark several messages when decode them with X u, it
tells me that a file already exists, ring the bell and stops the
decoding process.
I really would like it if it didn't ring the bell, and I need it to
continue with the next message instead of stopping.
What's wrong? How do I set up gnus to do this?
Thanks for any help.
next reply other threads:[~1999-06-22 6:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 6:26 Gerald [this message]
1999-07-04 2:26 ` Lars Magne Ingebrigtsen
1999-07-04 10:55 ` Per Abrahamsen
1999-07-04 11:14 ` Lars Magne Ingebrigtsen
1999-07-04 11:14 ` Per Abrahamsen
1999-07-04 11:46 ` 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=14191.11006.890236.809580@localhost \
--to=gutier@intergate.bc.ca \
/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).