From: The Ghost In The Machine <ewill@aurigae.athghost7038suus.net>
Subject: Re: Fatal error (11). Emacs/ Linux hosed my very long document.
Date: Sat, 18 Sep 2004 11:26:13 GMT [thread overview]
Message-ID: <iier12-ca9.ln1@lexi2.athghost7038suus.net> (raw)
In-Reply-To: <2qv41kF142tp6U1@uni-berlin.de>
In comp.os.linux.advocacy, Richard Taylor
<richard@rtaylor93.wanadoo.co.uk>
wrote
on Fri, 17 Sep 2004 04:28:31 +0100
<2qv41kF142tp6U1@uni-berlin.de>:
> Mike Cox wrote:
>
>> I recently switched to xemacs as my default word processor so I could
>> do formatting in TEX for a very long document. Most recently I've
>> been using Microsoft Word, the latest version. I switched because I
>> thought that emacs had perfect stability and no crashes. My
>> perception was formed due to the constant FSF/GPL/Linux advocacy
>> promoted on slashdot and all the comp newsgroups.
>>
>> I was also inspired by Paul Graham's claims that LISP will not core
>> dump and you can debug and get back to work.
>>
>> So with this background, I decided that my comprehensive review of
>> Linux, and GNU programs would be written using all open source tools
>> and operating systems. This review was to be submitted to several
>> news sites including slashdot and OSNEWS.
>>
>> Much to my dismay, as I was working on my very long review (about 100
>> pages typed), xemacs core dumped on me. I was unable to recover
>> anything. I didn't save my document because I never expected emacs to
>> core dump. The worst I thought would happen would be some LISP error.
>> Hopefully someone can debug emacs and fix this dangerous bug. Until
>> then, I'm probably going to go back to Microsoft Word 2003. THe
>> following is my core dump file:
>>
>
> I can see that all of your problems will be solved, as MS Word, in
> common with all MS software, has an excellent reputation as robust
> software which almost _never_ crashes, certainly not as often as
> GNU/Linux applications.
>
> Personally, I make a point to never save my work either. Certainly not
> once I'm getting close to the 100 page mark. Since my software is known
> to _never_ crash, what possible good could it do me to save a copy
> dozens of hours of hard work to my hard drive?
>
> Certainly, none of the problems you have experience could be laid at the
> feet of the user, as it is customary to expect that one can type a
> 100-page document without the slightest chance of:
>
> A) Loosing power,
>
> B) Hardware failiure
>
> C) Software failiure unrelated to word processor/text editor,
>
> D) General malign fate.
E) Cats walking over the keyboard.
F) Kids walking over Dad (or Mom) and inadvertantly doing things.
G) X11 crashes. (Hey, not even Linux is perfect. :-) )
H) Alien space beings knock at one's door and invite you to participate
in a variation of the Philadelphia Experiment, after tying you up with
a bale of copper wire and attaching it to an odd-looking contrivance
that looks suspiciously like an alien nuclear battery.
(OK, so I made the last one up. :-) )
>
> You have, of course, my deepest sympathies. Rest assured that I will
> never again take the risk of using or advocating XEmacs, GNU Emacs, or
> any other GNU Project/FSF software. After all, it's clearly not suitable
> for the needs of a /reasonable/ user.
>
Mike Cox? Reasonable? :-) Surely you jest...
In any event, I for one would not use Emacs (mostly because I never got
around to learning it) but that's beside the point; if one wants 100
pages of document, perhaps it makes more sense, especially for web
design, to generate 100 individual Webnodes?
Then again, that leads to renumbering and/or filename
problems. Any editor worth its salt (presumably that
includes Emacs, vi, and many others) will do the following:
[1] Open the file mydocument.whatever for readonly access, and read it
into memory or a scratchpad file somewhere.
[2] (Optional) Save the memory or scratchpad on an occasional basis.
[3] When saving, create the new file in mydocument.whatever.new or
.mydocument.whatever.new or ... well, whatever.
[4] After the save is confirmed (presumably by careful I/O checking;
each I/O call returns the number of bytes written -- another
method might be to check the size of the written file using stat()),
mydocument.whatever can be renamed to mydocument.whatever.bak
and .mydocument.whatever.new renamed to mydocument.whatever.
In vi, I write ':w' frequently anyway, just in case. (I don't know the
Emacs equivalent.)
--
#191, ewill3@earthlink.net
It's still legal to go .sigless.
next prev parent reply other threads:[~2004-09-18 11:26 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 [this message]
[not found] ` <m2wtysbw01.fsf@Stella-Blue.local>
[not found] ` <d60kym2k.fsf@gmail.com>
[not found] ` <x5brg3ucuw.fsf@lola.goethe.zz>
2004-09-18 10:54 ` Marcin 'Qrczak' Kowalczyk
[not found] ` <pan.2004.09.17.20.07.34.698482@that.google.thingy>
2004-09-18 22:07 ` Tim McNamara
[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] ` <DAF3d.21961$ZC7.12096@newssvr19.news.prodigy.com>
2004-09-20 21:13 ` Fatal error (11). Emacs/ Linux hosed my very long document 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=iier12-ca9.ln1@lexi2.athghost7038suus.net \
--to=ewill@aurigae.athghost7038suus.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).