[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Loading an output from prin1 (savehist bug).

From: Richard Stallman
Subject: Re: Loading an output from prin1 (savehist bug).
Date: Wed, 24 May 2006 15:21:01 -0400

    >   If some code output command-history with prin1 then try to load it
    >   back, the # things will cause parse errors.

We can't alter that.  I see a few possible solutions:

1. Don't put markers into arguments to interactive commands,
except thru the specific functions (point), (mark), etc.,
which go into command-history as calls to those functions.

2. Fix programs such as bbdb-create and savehist to find
such markers and replace them with nil.

3. Create a more general mechanism for commands to specify
how to record calls to them in command-history.

Solution #1 seems simplest; is there any reason why you need to put
these markers in args to commands?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]