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: Fri, 25 May 2007 20:19:38 -0400 [thread overview]
Message-ID: <E1Hrk0Q-0004Az-6L@fencepost.gnu.org> (raw)
In-Reply-To: <22565.1180017802@gemini.franz.com> (message from Kevin Layer on Thu, 24 May 2007 07:43:22 -0700)
then a lot more binary junk and then this:
**************************************** START
\x1ce/layer/mail/inbox-spam/\x01€×# /home/layer/mail/inbox-spam/#1#”×# \(:-[({]\)\(\W\|\'\))\b\x14Î# \(:-[/\]\)\(\W\|\'\)\x1e\x18 ôÍ# \([:;]-?)\)\(\W\|\'\))\b\x0678 \x0eore--99379 \x12tf-save--99380\b\x13tf-bound--99381\x19uffer named *Summary*)\bdÍ# \(\s-\|^\)\(_\(\(\w\|_[^_]\)+\)_\)\(\s-\|[?!.,;]\)\bDÍ# \(\
That is really strange because it looks like a file name got clobbered
near the beginning. `/hom' apparently was replaced by stuff ending in ^\.
I can't imagine what could do that.
These file names all look strange to me. Perhaps you are using a mail
reader that uses lots of file names in a pattern I don't recognize.
As a result, I can't tell what parts of this output is valid names.
Can you show the same output and point out which parts are part of
real meaningful file names, and what the whole file names look like?
next prev parent reply other threads:[~2007-05-26 0:19 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
2007-05-24 14:43 ` Kevin Layer
2007-05-26 0:19 ` Richard Stallman [this message]
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
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=E1Hrk0Q-0004Az-6L@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).