unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 8219@debbugs.gnu.org, emacs-devel@gnu.org
Subject: Re: bug#8219: Effect of deletions on indirect buffers (Bug#8219)
Date: Sat, 12 Mar 2011 10:15:05 +0200	[thread overview]
Message-ID: <834o78u54m.fsf@gnu.org> (raw)
In-Reply-To: <874o79nzla.fsf@stupidchicken.com>

> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: 8219@debbugs.gnu.org, emacs-devel@gnu.org
> Date: Fri, 11 Mar 2011 15:58:57 -0500
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Hence, in the aftermath of a deletion, buffer B's values of PT (and
> >> BUF_BEGV and BUF_ZV) can be larger than BUF_ZV.
> >
> > Isn't that a bug, right there?  Why doesn't del_range_2 update the
> > indirect buffer (B) as well, when deletion removes text so that its PT
> > becomes invalid?
> 
> This is not currently easy.  We don't keep track of indirect buffers
> (looping over the buffer list each time we do a deletion would be rather
> inefficient), so this would need some new members of the buffer struct.

We could do that lazily, whenever something (including redisplay) is
done on a buffer that happens to be an indirect buffer.



  reply	other threads:[~2011-03-12  8:15 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 [this message]
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
2011-03-14  2:41           ` bug#8219: " 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=834o78u54m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=8219@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@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).