all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: 7556-done@debbugs.gnu.org
Subject: bug#7556: 24.0.50; visiting an EPS file with preview TIFF image and with one long line
Date: Tue, 07 Dec 2010 20:44:39 +0200	[thread overview]
Message-ID: <83lj412zjc.fsf@gnu.org> (raw)
In-Reply-To: <765CAE6F-3A4D-4095-BD2E-5A56AE19E697@Freenet.DE>

> Cc: 7556@debbugs.gnu.org
> From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
> Date: Tue, 7 Dec 2010 10:43:33 +0100
> 
> The elder NS variant is faster than the X client and did not produce a  
> backup file. I did not wait until the up-to-date X client finished  
> scrolling or creating the backup file but killed it with xkill. *This*  
> produced the backup file. The date of this file and that of my action  
> is the same, to the minute. Previously I killed GNU Emacs when it  
> became inoperable and not knowing the cause of this behaviour. After  
> this I visited the directory in dired mode and saw the backup files  
> and concluded they might have been created when GNU Emacs started to  
> consume all CPU power–now in some irregular working mode–while in fact  
> this was perhaps a minute later when I killed it.

Yes, when Emacs catches a fatal signal, it auto-saves.  This is normal
behavior.

Closing.  Thanks for looking into this.






      reply	other threads:[~2010-12-07 18:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04 21:59 bug#7556: 24.0.50; visiting an EPS file with preview TIFF image and with one long line Peter Dyballa
2010-12-05  4:06 ` Eli Zaretskii
2010-12-05 12:04   ` Peter Dyballa
2010-12-05 14:37     ` Eli Zaretskii
2010-12-06  9:44       ` Peter Dyballa
2010-12-06 18:53         ` Eli Zaretskii
2010-12-06 21:05           ` Peter Dyballa
2010-12-07  9:43           ` Peter Dyballa
2010-12-07 18:44             ` Eli Zaretskii [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lj412zjc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=7556-done@debbugs.gnu.org \
    --cc=Peter_Dyballa@Freenet.DE \
    /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.