all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Kevin Layer <layer@franz.com>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: huge files in ~/.emacs.d/auto-save-list/
Date: Thu, 24 May 2007 06:55:31 -0400	[thread overview]
Message-ID: <E1HrAyh-0003je-Bm@fencepost.gnu.org> (raw)
In-Reply-To: <18578.1179948839@gemini.franz.com> (message from Kevin Layer on Wed, 23 May 2007 12:33:59 -0700)

    I found a couple of bad files at home.  One is 1mb, the other 17mb.  I
    use 21.4.1 on Linux (FC6) there.  There are definite good lines
    interspersed in between the junk.

Are the good lines complete?  Do they end with newlines?
Do they start with newlines?  At what kinds of points in the normal
and valid sequence of input does the junk get inserted?

    I can also say that the last bogus file in that directory definitely
    was written long after the last emacs crash I've had.

That doesn't surprise me, because we know that Emacs continued after
writing the junk, and wrote more good lines.

  reply	other threads:[~2007-05-24 10:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 20:39 huge files in ~/.emacs.d/auto-save-list/ Kevin Layer
2007-05-21 20:55 ` Eli Zaretskii
2007-05-21 21:47   ` Kevin Layer
2007-05-22 14:52 ` Richard Stallman
2007-05-22 15:06   ` Kevin Layer
2007-05-22 23:10     ` Richard Stallman
2007-05-22 23:26       ` Kevin Layer
2007-05-23 18:56         ` Richard Stallman
2007-05-23 19:33           ` Kevin Layer
2007-05-24 10:55             ` Richard Stallman [this message]
2007-05-24 14:43               ` Kevin Layer
2007-05-26  0:19                 ` Richard Stallman
2007-05-23 19:42           ` Kevin Layer
2007-05-23  9:32       ` Andreas Schwab
2007-05-23 11:47         ` Eli Zaretskii
2007-05-23 23:45           ` Richard Stallman
2007-05-23 18:56         ` Richard Stallman

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=E1HrAyh-0003je-Bm@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=layer@franz.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.