unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, 8219@debbugs.gnu.org, emacs-devel@gnu.org
Subject: Re: Effect of deletions on indirect buffers (Bug#8219)
Date: Sun, 13 Mar 2011 18:29:01 -0400	[thread overview]
Message-ID: <87wrk2vemq.fsf@stupidchicken.com> (raw)
In-Reply-To: <jwvipvooyog.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 12 Mar 2011 15:47:05 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> /* !!!FIXME:  all the BUF_BEGV/BUF_ZV/BUF_PT macros are flawed:
>    on indirect (or base) buffers, that value is only correct if that buffer
>    is the current_buffer, or if the buffer's text hasn't been modified (via
>    an indirect buffer) since it was last current.  */

OK, I've committed a fix to trunk.  Instead of doing away with the BUF_*
macros, I reworked them to handle the indirect buffer case properly.
This means they can no longer be used in `BUF_PT (foo) = bar' assignment
statements, so I've changed the callers that used them this way.

Not sure if the patch is appropriate for the emacs-23 branch, though.



  parent reply	other threads:[~2011-03-13 22:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 19:48 Effect of deletions on indirect buffers (Bug#8219) Chong Yidong
2011-03-11 20:07 ` Eli Zaretskii
2011-03-11 20:58   ` bug#8219: " Chong Yidong
2011-03-12  8:15     ` Eli Zaretskii
2011-03-11 23:19   ` Stefan Monnier
2011-03-12  9:01     ` Eli Zaretskii
2011-03-12 20:47       ` Stefan Monnier
2011-03-13 16:30         ` bug#8219: " Chong Yidong
2011-03-13 17:09           ` Chong Yidong
2011-03-13 22:29         ` Chong Yidong [this message]
2011-03-14  2:41           ` Juanma Barranquero
2011-03-14 16:18             ` Chong Yidong

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=87wrk2vemq.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=8219@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).