[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Loading an output from prin1 (savehist bug).
From: |
Michaël Cadilhac |
Subject: |
Re: Loading an output from prin1 (savehist bug). |
Date: |
Thu, 25 May 2006 13:40:48 +0200 |
User-agent: |
Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux) |
Richard Stallman <address@hidden> writes:
> > 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?
I don't have one ; that was just because bbdb seems to do.
Does this restriction have to be put in the coding style section of
the manual?
--
| Michaël `Micha' Cadilhac | Pour les 35-40 ans, l'humour |
| Epita/LRDE Promo 2007 | c'est une plus-value. |
| http://www.lrde.org/~cadilh_m | -- Guillaume L. |
`-- - JID: address@hidden --' - --'
pgpoQJM76rHIj.pgp
Description: PGP signature