From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Autosaving shrunk buffers
Date: Mon, 11 Dec 2006 14:14:30 -0700 [thread overview]
Message-ID: <elkhp5$u1r$1@sea.gmane.org> (raw)
In-Reply-To: <1165853120.796675.240320@16g2000cwy.googlegroups.com>
Yevgeniy Makarov wrote:
> This topic has been raised in this group before--in 1991 and
> 2002--however, no answer was given.
>
> How do I convince Emacs not to turn off auto-saving when a buffer has
> shrunk a lot?
*** fileio.c.orig 2006-12-04 08:16:47 -0000
--- fileio.c 2006-12-11 14:11:13 -0700
***************
*** 5975,5980 ****
--- 5975,5981 ----
&& EMACS_SECS (before_time) - b->auto_save_failure_time < 1200)
continue;
+ #if 0
if ((XFASTINT (b->save_length) * 10
> (BUF_Z (b) - BUF_BEG (b)) * 13)
/* A short file is likely to change a large fraction;
***************
*** 5995,6000 ****
--- 5996,6002 ----
Fsleep_for (make_number (1), Qnil);
continue;
}
+ #endif
set_buffer_internal (b);
if (!auto_saved && NILP (no_message))
message1 ("Auto-saving...");
--
Kevin
prev parent reply other threads:[~2006-12-11 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 16:05 Autosaving shrunk buffers Yevgeniy Makarov
2006-12-11 21:14 ` Kevin Rodgers [this message]
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='elkhp5$u1r$1@sea.gmane.org' \
--to=ihs_4664@yahoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).