unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Gnus accumulating copies of a draft when sending is not possible
Date: Fri, 22 Oct 2021 09:50:21 +0200	[thread overview]
Message-ID: <87tuh9o5vm.fsf@web.de> (raw)
In-Reply-To: 87tuh9o83l.fsf@ucl.ac.uk

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Do you by any chance have numbered backup files?  Check the value of
> the =version-control= variable.

Well - I see the same.  After a failed sending attempt there seems to be
a modified message buffer, and when exiting Gnus that buffer seems to be
saved as a new draft each time.  Toggling `version-control' doesn't make
a difference.

Has anybody actually tried to reproduce???  I just used an address like
"test" and tried to send.

> Maybe have a look at the contents of the ~/News/drafts/drafts
> directory?  (or elsewhere if you change the default location)

Doesn't look like numbered backups.  Looks like normal files
corresponding to the draft copies one sees in Gnus.

Michael.




  reply	other threads:[~2021-10-22  7:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 21:00 Gnus accumulating copies of a draft when sending is not possible H. Dieter Wilhelm
2021-10-20  8:14 ` Lars Ingebrigtsen
2021-10-20 20:21   ` H. Dieter Wilhelm
2021-10-21 13:14     ` Lars Ingebrigtsen
2021-10-22  6:42       ` H. Dieter Wilhelm
2021-10-22  7:02         ` Eric S Fraga
2021-10-22  7:50           ` Michael Heerdegen [this message]
2021-10-22 21:04             ` H. Dieter Wilhelm
2021-10-23  8:07               ` Michael Heerdegen
2021-10-28  6:34                 ` H. Dieter Wilhelm
2021-10-28 10:03                   ` Michael Heerdegen
2021-10-22 16:54         ` Lars Ingebrigtsen
2021-10-23  8:16           ` Michael Heerdegen
2021-10-23 16:10             ` Eric Abrahamsen
2021-10-24  7:54               ` Michael Heerdegen
2021-10-24 13:38                 ` Lars Ingebrigtsen
2021-10-24 14:53                   ` Michael Heerdegen
2021-10-24 15:17                     ` Michael Heerdegen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tuh9o5vm.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).