unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13007@debbugs.gnu.org, lekktu@gmail.com,
	Dmitry Antipov <dmantipov@yandex.ru>
Subject: bug#13007: 24.3.50; emacs_backtrace.txt
Date: Tue, 29 Dec 2015 12:08:49 +0100	[thread overview]
Message-ID: <87si2lldfi.fsf@gnus.org> (raw)
In-Reply-To: <83a9tzv2m0.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 30 Nov 2012 11:53:11 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Function set_window_buffer (W, B, ...) is called where W is selected_window
>> and XBUFFER (B) != current_buffer. This function temporary sets current
>> buffer to XBUFFER (B) to run hooks, and then restore old current_buffer [1].
>> So, on exit we have XBUFFER (XWINDOW (selected_window)->buffer) != current_buffer,
>> and these gets _finally_ synchronized only when read_key_sequence is called with
>> fix_current_buffer == true [2]. If redisplay is invoked between [1] and [2],
>> its routines may see the condition which was eassert'ed; _finally_ means
>> that some redisplay routines may do the synchronization temporary and
>> then restore original value of current buffer (see pos_visible_p for example).
>
> OK.  So what do you suggest, in practical terms?  Are you saying that
> we should use BUF_MODIFF(XBUFFER (w->buffer)) instead of MODIFF and
> BUF_OVERLAY_MODIFF(XBUFFER (w->buffer)) instead of OVERLAY_MODIFF
> inside window_outdated?  Or do you suggest something else?
>
> I'm okay with using BUF_* macros in window_outdated.

It's unclear what the conclusion here was.  Is there anything more to be
done in this bug report?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2015-12-29 11:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27  6:23 bug#13007: 24.3.50; emacs_backtrace.txt Drew Adams
2012-11-27  6:28 ` Drew Adams
2012-11-27 15:15   ` Eli Zaretskii
2012-11-27 15:41     ` Drew Adams
2012-11-27 15:44       ` Drew Adams
2012-11-27 16:39     ` Juanma Barranquero
2012-11-27 18:02       ` Eli Zaretskii
2012-11-27 15:14 ` Eli Zaretskii
2012-11-27 16:49   ` Dmitry Antipov
2012-11-27 17:47     ` Eli Zaretskii
2012-11-27 17:58       ` Jambunathan K
2012-11-27 18:10         ` Drew Adams
2012-11-28  7:19       ` Dmitry Antipov
2012-11-28 13:09         ` Juanma Barranquero
2012-11-28 15:51           ` Dmitry Antipov
2012-11-28 17:59             ` Eli Zaretskii
2012-11-29  6:19               ` Dmitry Antipov
2012-11-29 16:46                 ` Eli Zaretskii
2012-11-29 17:02                   ` Drew Adams
2012-11-29 17:39                     ` Eli Zaretskii
2012-11-29 17:47                       ` Drew Adams
2012-11-29 18:08                         ` Eli Zaretskii
2012-11-29 18:13                           ` Drew Adams
2012-11-29 19:50                             ` Eli Zaretskii
2012-11-29 17:23                   ` Dmitry Antipov
2012-11-30  9:53                     ` Eli Zaretskii
2012-11-30 15:50                       ` Dmitry Antipov
2012-11-30 16:59                         ` Eli Zaretskii
2015-12-29 11:08                       ` Lars Ingebrigtsen [this message]
2015-12-29 17:37                         ` Eli Zaretskii
2016-01-02 11:10                           ` Eli Zaretskii
2012-11-29 19:14                   ` Stefan Monnier
2012-11-29 19:54                     ` Eli Zaretskii

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=87si2lldfi.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=13007@debbugs.gnu.org \
    --cc=dmantipov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=lekktu@gmail.com \
    /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).