From: Harry Putnam <reader@newsguy.com>
Subject: Re: Is this a buglet.. nndrafts:draft renegades
Date: Wed, 07 Nov 2001 11:03:15 -0800 [thread overview]
Message-ID: <m1668m76a4.fsf@reader.newsguy.com> (raw)
In-Reply-To: <87lmhi78ke.fsf@harpo.homeip.net> (Samuel Padgett's message of "Wed, 07 Nov 2001 13:13:53 -0500")
Samuel Padgett <spadgett1@nc.rr.com> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> Samuel Padgett <spadgett1@nc.rr.com> writes:
>>
>>> I got this response from RMS:
>>>
>>> I decided to change the code to fix the documentation.
>>> Thanks for reporting the bug.
>>>
>>> I guess this is a doc bug then?
>>
>> Hard to tell what is meant there. Sounds like it means the doc is
>> right and the behavior wrong. I hope not..
>
> I asked Richard for clarification, and he said he changed the behavior
> to match what the doc says.
Let me make sure I'm following here.
Existing doc says:
delete-auto-save-files's value is t
Documentation:
*Non-nil means delete auto-save file when a buffer is saved or killed.
Note that auto-save file will not be deleted if the buffer is killed
when it has unsaved changes.
So the new behavior in future releases will be in accord with that
documentation:
If one `C-x C-f file' when no actual file is on disk, then types into
it. Then aborts with `C-x k <YES>' An auto-save file will remain on
disk. That is, piles of #file# will soon develop. At least with my
usage pattern.
20.7 doesn't do that either. At least not by default.
Is that your take on RMSs' response?
next prev parent reply other threads:[~2001-11-07 19:03 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 21:29 Harry Putnam
2001-11-02 21:46 ` Matt Armstrong
2001-11-03 1:06 ` Harry Putnam
2001-11-03 14:23 ` Per Abrahamsen
2001-11-03 20:29 ` Russ Allbery
2001-11-03 2:08 ` Russ Allbery
2001-11-03 3:01 ` Harry Putnam
2001-11-03 3:06 ` Karl Kleinpaste
2001-11-03 3:19 ` Samuel Padgett
2001-11-03 14:25 ` Per Abrahamsen
2001-11-03 14:56 ` ShengHuo ZHU
2001-11-03 15:54 ` Samuel Padgett
2001-11-03 19:32 ` Matt Armstrong
2001-11-03 21:10 ` Matt Armstrong
2001-11-03 22:25 ` Samuel Padgett
2001-11-03 23:47 ` Harry Putnam
2001-11-04 0:16 ` Samuel Padgett
2001-11-04 1:17 ` Harry Putnam
2001-11-04 1:47 ` Samuel Padgett
2001-11-04 2:13 ` Samuel Padgett
2001-11-03 23:40 ` Harry Putnam
2001-11-05 10:53 ` Per Abrahamsen
2001-11-05 16:22 ` Harry Putnam
2001-11-05 17:30 ` Samuel Padgett
2001-11-05 19:21 ` Harry Putnam
2001-11-05 17:04 ` Matt Armstrong
2001-11-05 17:26 ` Samuel Padgett
2001-11-05 18:21 ` Matt Armstrong
2001-11-06 9:29 ` Per Abrahamsen
2001-11-06 14:05 ` Samuel Padgett
2001-11-06 15:41 ` Harry Putnam
2001-11-07 18:13 ` Samuel Padgett
2001-11-07 19:03 ` Harry Putnam [this message]
2001-11-07 22:21 ` Samuel Padgett
2001-11-04 18:22 ` Kai Großjohann
2001-11-04 18:31 ` Samuel Padgett
2001-11-04 18:46 ` Kai Großjohann
2001-11-04 19:20 ` Matt Armstrong
2001-11-04 20:24 ` Samuel Padgett
2001-11-05 17:06 ` Paul Jarc
2001-11-05 17:19 ` Matt Armstrong
2001-11-05 17:48 ` Samuel Padgett
2001-11-05 17:22 ` Samuel Padgett
2001-11-05 17:32 ` Paul Jarc
2001-11-05 17:56 ` Samuel Padgett
2001-11-03 15:40 ` Samuel Padgett
2001-11-03 3:56 ` Russ Allbery
2001-11-03 16:22 ` Kai Großjohann
2001-11-03 16:20 ` Kai Großjohann
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=m1668m76a4.fsf@reader.newsguy.com \
--to=reader@newsguy.com \
/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).