Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tim McNamara <timmcn@bitstream.net>
Subject: Re: Fatal error (11).  Emacs/ Linux hosed my very long document.
Date: Sat, 18 Sep 2004 17:07:38 -0500	[thread overview]
Message-ID: <m2y8j7mdsl.fsf@Stella-Blue.local> (raw)
In-Reply-To: <pan.2004.09.17.20.07.34.698482@that.google.thingy>

Craig Kelley <namonai@that.google.thingy> writes:

> On Fri, 17 Sep 2004 13:17:34 -0500, Tim McNamara wrote:
>
>> 4.  Emacs by default creates backup documents, you'll find them in
>>     the same directory as the file you were working on with a tilde
>>     after the filename.  Hopefully XEmacs, which I've never used,
>>     does the same thing.
>
> The tilde document is the last version; the auto backup will be the
> filename surrounded by hash marks (#).

Thanks for that- if Emacs ever crashes while I'm editing a docuent,
I'll know what to look for.


  parent reply	other threads:[~2004-09-18 22:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3d6111f1.0409161437.30ef8b7d@posting.google.com>
2004-09-17  0:08 ` Floyd L. Davidson
2004-09-17  6:02 ` David Kastrup
     [not found] ` <2qv41kF142tp6U1@uni-berlin.de>
2004-09-18 11:26   ` The Ghost In The Machine
     [not found] ` <m2wtysbw01.fsf@Stella-Blue.local>
     [not found]   ` <2r14t7F14lvf5U1@uni-berlin.de>
2004-09-18  7:30     ` Which is better, xemacs or gnu emacs? Aquila Deus
2004-09-18 22:14     ` Tim McNamara
2004-09-18 22:25       ` kier
     [not found]   ` <d60kym2k.fsf@gmail.com>
     [not found]     ` <x5brg3ucuw.fsf@lola.goethe.zz>
2004-09-18 10:54       ` Fatal error (11). Emacs/ Linux hosed my very long document Marcin 'Qrczak' Kowalczyk
     [not found]   ` <pan.2004.09.17.20.07.34.698482@that.google.thingy>
2004-09-18 22:07     ` Tim McNamara [this message]
     [not found] ` <DAF3d.21961$ZC7.12096@newssvr19.news.prodigy.com>
2004-09-20 21:13   ` David Kastrup
     [not found]     ` <2r90j7F17iuf3U1@uni-berlin.de>
     [not found]       ` <x5k6uoa9ci.fsf@lola.goethe.zz>
     [not found]         ` <2r96g3F182tnvU1@uni-berlin.de>
2004-09-21  0:08           ` Josh
     [not found]           ` <x5fz5c89yg.fsf@lola.goethe.zz>
     [not found]             ` <2ra052F18agplU1@uni-berlin.de>
     [not found]               ` <x58yb4853b.fsf@lola.goethe.zz>
2004-09-21 22:50                 ` Mike Cox
2004-09-28 12:48                   ` Miles Bader
     [not found]                     ` <2rtt5bF1cs38gU2@uni-berlin.de>
     [not found]                       ` <87d605yfac.fsf@tleepslib.sk.tsukuba.ac.jp>
     [not found]                         ` <87k6ubq2u0.fsf@tc-1-100.kawasaki.gol.ne.jp>
     [not found]                           ` <87d603b1e9.fsf@tleepslib.sk.tsukuba.ac.jp>
2004-10-01 23:19                             ` Miles Bader
2004-10-02  6:58                               ` Stephen J. Turnbull

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=m2y8j7mdsl.fsf@Stella-Blue.local \
    --to=timmcn@bitstream.net \
    /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 NNTP newsgroup(s).