From: "spamfilteraccount@gmail.com" <spamfilteraccount@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: Invalid read syntax when using savehist.el
Date: Mon, 26 Nov 2007 22:13:10 -0800 (PST) [thread overview]
Message-ID: <d7a5f2be-f75e-4f46-9ec3-f0b41f90ec4d@r31g2000hsg.googlegroups.com> (raw)
I have savehist turned on and yesterday startup of emacs failed with
an invalid read syntax error.
Turned out the problem was caused by a kbd macro which savehist stored
like this:
(setq command-history '( ... (execute-kbd-macro [19 107 (language-
change (#<frame ...
I assume the reader choked on the #<... part, because everything was
fine when I removed it.
GNU Emacs 22.1.1 (i386-mingw-nt5.1.2600) of 2007-06-02 on RELEASE
next reply other threads:[~2007-11-27 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 6:13 spamfilteraccount [this message]
2007-11-27 6:17 ` Invalid read syntax when using savehist.el spamfilteraccount
2007-11-28 22:40 ` Reiner Steib
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=d7a5f2be-f75e-4f46-9ec3-f0b41f90ec4d@r31g2000hsg.googlegroups.com \
--to=spamfilteraccount@gmail.com \
--cc=bug-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).