From: storm@cua.dk (Kim F. Storm)
To: Miles Bader <miles@gnu.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: EMACS22: Unexpected question when fetching mail in Gnus...
Date: Sat, 08 Mar 2008 19:04:05 +0100 [thread overview]
Message-ID: <87fxv13xey.fsf@kfs-lx.rd.rdm> (raw)
In-Reply-To: <874pbh9xyg.fsf@catnip.gol.com> (Miles Bader's message of "Sat\, 08 Mar 2008 21\:55\:51 +0900")
Miles Bader <miles@gnu.org> writes:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> I wonder why nobody using Emacs trunk or No Gnus complained about the
>> questions yet. (I'll make it clearer what the question is all about.)
>
> I just figured it was some safety thing (which seems reasonable) and
> customized mail-source-delete-old-incoming-confirm to nil...
When I test software, I try not to be that clever :-)
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2008-03-08 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pru6w0m3.fsf@kfs-lx.rd.rdm>
2008-03-08 11:09 ` Reiner Steib
2008-03-08 12:55 ` Miles Bader
2008-03-08 13:37 ` Norman Walsh
2008-03-08 16:20 ` Reiner Steib
2008-03-08 18:04 ` Kim F. Storm [this message]
2008-03-08 18:52 ` Reiner Steib
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=87fxv13xey.fsf@kfs-lx.rd.rdm \
--to=storm@cua.dk \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.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).