From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Backing up buffers
Date: Sun, 21 Jan 2007 22:57:41 +0200 [thread overview]
Message-ID: <ufya4drne.fsf@gnu.org> (raw)
In-Reply-To: <1169396340.051009.161280@l53g2000cwa.googlegroups.com> (rbielaws@i1.net)
> From: "rgb" <rbielaws@i1.net>
> Date: 21 Jan 2007 08:19:00 -0800
>
> are you saying that autosave can already be configured
> to save the contents of buffers that don't have files
> associated with them?
All you need is to turn on auto-save; it is off by default in such
buffers. You could arrange for the appropriate mode hook to do that.
You can find an example in mail-mode, which arranges for the *mail*
buffers, where you compose outgoing messages, to be auto-saved.
next prev parent reply other threads:[~2007-01-21 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 17:53 Backing up buffers HS
2007-01-19 22:03 ` rgb
2007-01-19 23:47 ` Matthew Flaschen
2007-01-20 13:28 ` Eli Zaretskii
2007-01-22 14:05 ` Matthew Flaschen
[not found] ` <mailman.3345.1169299706.2155.help-gnu-emacs@gnu.org>
2007-01-21 16:19 ` rgb
2007-01-21 20:57 ` Eli Zaretskii [this message]
[not found] ` <mailman.3391.1169413066.2155.help-gnu-emacs@gnu.org>
2007-01-22 13:00 ` HS
2007-01-20 13:27 ` Eli Zaretskii
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=ufya4drne.fsf@gnu.org \
--to=eliz@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.
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).