From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: Re: revert-buffer tragedy
Date: 23 Apr 2005 19:49:31 -0500 [thread overview]
Message-ID: <wizmvpj8x0.fsf@dms.auburn.edu> (raw)
In-Reply-To: d4cb61$am1$1@mughi.cs.ubc.ca
Lowell Kirsh wrote:
I just lost hours of work due to a combination of auto-revert-buffer
and accidentally overwriting a file in my shell.
I do not know what shell you were using and how you accidentally
overwrote your file from the shell. But if you were using bash and
overwrote using output redirection, you could write:
set -C
in your .bashrc. That will only protect against accidental overwiting
using output redirection (using `>', `>&', and `<>'), however.
Sincerely,
Luc.
prev parent reply other threads:[~2005-04-24 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 2:16 revert-buffer tragedy Lowell Kirsh
2005-04-23 4:48 ` Denis Bueno
2005-04-23 7:23 ` ken
2005-04-23 8:01 ` Adrian Aichner
2005-04-24 0:32 ` Lowell Kirsh
2005-04-24 0:49 ` Luc Teirlinck [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
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=wizmvpj8x0.fsf@dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).