From: Andy Stewart <lazycat.manatee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Relative n00by question: >>End of file during parsing<< Error with simple backup unifier script
Date: Sat, 06 Sep 2008 15:21:05 +0800 [thread overview]
Message-ID: <87k5dpbuzi.fsf@manatee.domain> (raw)
In-Reply-To: mailman.17672.1219843891.18990.help-gnu-emacs@gnu.org
Hi.
I think bug is at behind 'version-control t', and lost ')'.
So right is:
(setq backup-by-copying t ; don't clobber symlinks
'(("." . "~/emacsbackups")) ; don't litter my fs tree
delete-old-versions t
kept-new-versions 6
kept-old-versions 2
version-control t ; use versioned backups
) ;; bug is at this, add this!!!
Andy.
Regards.
next prev parent reply other threads:[~2008-09-06 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.17672.1219843891.18990.help-gnu-emacs@gnu.org>
2008-09-06 7:09 ` Relative n00by question: >>End of file during parsing<< Error with simple backup unifier script Andy Stewart
2008-09-06 7:11 ` Andy Stewart
2008-09-06 7:21 ` Andy Stewart [this message]
2008-08-27 11:18 straylightblue
2008-08-27 13:50 ` Lennart Borgman (gmail)
2008-08-27 15:27 ` Peter Dyballa
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=87k5dpbuzi.fsf@manatee.domain \
--to=lazycat.manatee@gmail.com \
--cc=help-gnu-emacs@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).