all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Blicher <blicher@research.nj.nec.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: autosave
Date: Tue, 11 Jun 2002 14:10:50 -0400 (EDT)	[thread overview]
Message-ID: <200206111810.g5BIAoCU012881@mail.nj.nec.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020611073526.2609A-100000@is> (message from Eli Zaretskii on Tue, 11 Jun 2002 07:39:27 +0300 (IDT))

   Date: Tue, 11 Jun 2002 07:39:27 +0300 (IDT)
   From: Eli Zaretskii <eliz@is.elta.co.il>
   X-Sender: eliz@is
   cc: blicher@research.nj.nec.com, emacs-devel@gnu.org
   Content-Type: TEXT/PLAIN; charset=US-ASCII
   Content-Length: 693


   On Mon, 10 Jun 2002, Richard Stallman wrote:

   >     Oh, I guess I should mention a couple of other things:
   > 
   > Actually the one thing I would like is a complete self-contained
   > recipe for making the bug happen.  It is not normal for Emacs to write
   > auto-save files in emacs.d.

   The ~/.emacs.d/auto-save-list/ directory is used for the `.saves-*' files 
   where Emacs saves session information (used by "M-x recover-session").  
   (See startup.el:auto-save-list-file-prefix.)

   These are not the normal auto-save files, but they do resemble them 
   because Emacs saves session info periodically, like it does with 
   auto-saving.  Perhaps the problem was with those files, not with autosave 
   files.

That's highly likely.  However, given that rms has said he already looked at
the code, I think he is right that I will have to isolate the problem better
before you guys can do more.  Unless he did not look at the session save
code.

Unfortunately, it is hard to look at something like the *Messages* buffer
when the program is in an infinite loop of failed file operations.  Since
it's been years since I did emacs debugging, I don't remember offhand all the
stuff I have to do to debug, trace, etc., which means I have to look all this
stuff up before I can give you a distilled version of the problem.

--peer

-- 
A. Peter Blicher        NEC Research Institute
609-951-2716            4 Independence Way
609-951-2488 fax        Princeton, NJ  08540-6634  USA
blicher@research.nj.nec.com

  reply	other threads:[~2002-06-11 18:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-08  1:00 autosave Peter Blicher
2002-06-09 15:19 ` autosave Richard Stallman
2002-06-09 16:53   ` autosave Peter Blicher
2002-06-10 23:43     ` autosave Richard Stallman
2002-06-09 17:05   ` autosave Peter Blicher
2002-06-10 23:44     ` autosave Richard Stallman
2002-06-11  4:39       ` autosave Eli Zaretskii
2002-06-11 18:10         ` Peter Blicher [this message]
2002-06-12  4:46           ` autosave Eli Zaretskii
2002-06-12  2:31         ` autosave Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2003-10-17 19:37 Autosave Dave Saville

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=200206111810.g5BIAoCU012881@mail.nj.nec.com \
    --to=blicher@research.nj.nec.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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.