From: Greg Stark <gsstark@mit.edu>
Subject: message-mode trying to auto-save bogus file names
Date: 07 Aug 1999 23:48:03 -0400 [thread overview]
Message-ID: <87g11v9bm4.fsf@x2-312.mtl.Generation.NET> (raw)
I just recently upgraded to pgnus from whatever shipped with 20.3 and I'm
finding a few minor problems. Right now my drafts folder, which had been
working flawlessly is doing something strange.
Firstly the drafts folder appears to be ~/News/drafts/drafts which seems
strange enough, but then I see things like:
buffer-auto-save-file-name's value is
"/home/stark/Mail/drafts/#*message*#"
There are at least two things wrong with that variable, for one it's the wrong
directory, for another that's a pretty bad choice of filenames. It seems to me
we should just set auto-save-visited-file-name to t for drafts files anyways.
Also, it's really annoying to be asked if i want to save a mail when i haven't
written anything in it yet. It would be nice to flip the modified flag off
just after setting up the headers.
--
greg
next reply other threads:[~1999-08-08 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-08 3:48 Greg Stark [this message]
1999-09-24 17:51 ` 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=87g11v9bm4.fsf@x2-312.mtl.Generation.NET \
--to=gsstark@mit.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).