unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: michael.cadilhac@lrde.org (Michaël Cadilhac)
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: Loading an output from prin1 (savehist bug).
Date: Thu, 25 May 2006 13:40:48 +0200	[thread overview]
Message-ID: <8764jubadb.fsf@lrde.org> (raw)
In-Reply-To: <E1Fiyuj-0006C9-Bg@fencepost.gnu.org> (Richard Stallman's message of "Wed, 24 May 2006 15:21:01 -0400")


[-- Attachment #1.1: Type: text/plain, Size: 1228 bytes --]

Richard Stallman <rms@gnu.org> 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: micha@amessage.be --'                                   -  --'

[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

       reply	other threads:[~2006-05-25 11:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874q07xfm5.fsf@lrde.org>
     [not found] ` <87odxoslsr.fsf@lrde.org>
     [not found]   ` <E1Fiyuj-0006C9-Bg@fencepost.gnu.org>
2006-05-25 11:40     ` Michaël Cadilhac [this message]
2006-05-25 14:23       ` Loading an output from prin1 (savehist bug) Stefan Monnier
2006-05-26  2:22         ` Richard Stallman
2006-05-26 13:52         ` Johan Bockgård
2006-05-26  2:21       ` Richard Stallman
2006-06-10 16:00         ` Michaël Cadilhac
2006-06-11 10:28           ` Richard Stallman

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=8764jubadb.fsf@lrde.org \
    --to=michael.cadilhac@lrde.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@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).