unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: undo weirdness with insert-file-contents
Date: Thu, 28 Feb 2008 16:35:08 -0500	[thread overview]
Message-ID: <jwvzltkzryg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <47C70C24.6000302@gmx.at> (martin rudalics's message of "Thu, 28 Feb 2008 20:31:48 +0100")

>> I recommend you compile your Emacs with -DUSE_LISP_UNION_TYPE so the
>> compiler will explain to you where you're going wrong: XCAR (tem) is
>> a Lisp_Object, not an integer, so it cannot be compared with ==, but
>> only with EQ (which doesn't strike me as particularly non-intelligent in
>> this instance).

> Indeed.  Miles please try to debug with the attached patch instead.

> *** fileio.c.~1.602.~	Thu Feb 14 20:41:44 2008
> --- fileio.c	Thu Feb 28 20:21:18 2008
> ***************
> *** 4674,4680 ****
  
>         /* Save old undo list and don't record undo for decoding. */
>         old_undo = current_buffer->undo_list;
> -       current_buffer->undo_list = Qt;
  
But this patch is clearly problematic, if one believe the comment: it
would cause the generation of undo info during the decoding step.
I understand that this info will be thrown away later, but we don't want
to pay the corresponding price.


        Stefan




  parent reply	other threads:[~2008-02-28 21:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28  7:46 undo weirdness with insert-file-contents Miles Bader
2008-02-28  9:56 ` martin rudalics
2008-02-28 11:01   ` Miles Bader
2008-02-28 13:12     ` martin rudalics
2008-02-28 16:52       ` Stefan Monnier
2008-02-28 19:31         ` martin rudalics
2008-02-28 20:01           ` Miles Bader
2008-02-28 22:19             ` martin rudalics
2008-02-28 21:35           ` Stefan Monnier [this message]
2008-02-28 22:21             ` martin rudalics
2008-02-28 17:45 ` Glenn Morris
2008-02-28 19:35   ` martin rudalics
2008-02-28 20:28     ` Glenn Morris
2008-02-28 22:20       ` martin rudalics
2008-02-29 22:42       ` martin rudalics
2008-03-02  5:02         ` Stefan Monnier
2008-03-02 12:44           ` martin rudalics
2008-03-02 19:07             ` Stefan Monnier
2008-03-02 22:05               ` martin rudalics
2008-03-03  2:15                 ` Stefan Monnier
2008-03-03  9:09                   ` martin rudalics
2008-03-03 21:03                     ` Stefan Monnier
2008-03-07  9:33                       ` martin rudalics
2008-03-07 22:04                         ` Stefan Monnier
2008-03-08  9:55                           ` martin rudalics
2008-03-02 22:18               ` Bill Wohler
2008-03-03  9:09                 ` martin rudalics
2008-02-29  5:50   ` Bill Wohler

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=jwvzltkzryg.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=rudalics@gmx.at \
    /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).