From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Can we make set_point_both less expensive? Date: Fri, 20 Mar 2015 15:20:44 +0100 Message-ID: References: <5505E34C.4000106@dancol.org> <838uex1u1m.fsf@gnu.org> <8361a029p2.fsf@gnu.org> <83vbi0zukw.fsf@gnu.org> <55080104.9070606@gmx.at> <5508800E.3070600@gmx.at> <55092AE0.1080206@gmx.at> <5509CC67.5010207@gmx.at> <550A7FFB.7040502@gmx.at> <550BD579.9040804@gmx.at> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1426861306 3592 80.91.229.3 (20 Mar 2015 14:21:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 20 Mar 2015 14:21:46 +0000 (UTC) Cc: martin rudalics , Eli Zaretskii , Daniel Colascione , Emacs-Devel devel To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 20 15:21:45 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YYxny-0003S1-5W for ged-emacs-devel@m.gmane.org; Fri, 20 Mar 2015 15:21:42 +0100 Original-Received: from localhost ([::1]:44080 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYxnx-0004QR-Ht for ged-emacs-devel@m.gmane.org; Fri, 20 Mar 2015 10:21:41 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37975) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYxns-0004NP-LK for emacs-devel@gnu.org; Fri, 20 Mar 2015 10:21:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YYxnp-00006E-QF for emacs-devel@gnu.org; Fri, 20 Mar 2015 10:21:36 -0400 Original-Received: from mail-we0-x231.google.com ([2a00:1450:400c:c03::231]:34976) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYxni-0008WC-C5; Fri, 20 Mar 2015 10:21:26 -0400 Original-Received: by webcq43 with SMTP id cq43so83403187web.2; Fri, 20 Mar 2015 07:21:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Dp5y6FHdKv147hT918yVMICCtt/OY8e/TH0+7RnIJRw=; b=GN4thOXaPQ+KQ72atgdvV5YBmbkK+5VF30z5Mw48B1a6QtnoRpNRNVzdQTl/52uxbP tpmpEtDGsNZyj805EnH7Mu6R1vMlnV5YSGj39nWY5fq/LQWd0iY0jK5aqOkJX+c1qnWc 5Y7Gfi7TfWF3fDtjMnhqmWzAq2pu2FtStiKpD2weNS2MUUPN8JFbw6u0X8wqHaMFPdXW gac3SYdb7YNSRQi/BeTvsPF4hmsCkH+w0zY+WEwjISR14sC031FnyaJRCM/2SNCjY3Ru nai8TQn6vzL6Elk1yw4YLJsMFaH35HKupfV+JZWxn0nRWed4v6c9BbDZ+2GCTGfys7Z0 mRPg== X-Received: by 10.194.203.98 with SMTP id kp2mr21439537wjc.47.1426861285229; Fri, 20 Mar 2015 07:21:25 -0700 (PDT) Original-Received: by 10.194.51.226 with HTTP; Fri, 20 Mar 2015 07:20:44 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c03::231 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:184038 Archived-At: On Fri, Mar 20, 2015 at 3:14 PM, Stefan Monnier wrote: > > For me, a bad interaction is one where p-r-f followed by redisplay > followed by p-r-f followed by redisplay doesn't give the right answer. > > But with something like `cursor-intangible', there will surely be cases > where that can happen. E.g. imagine you scroll to a part of the buffer > that's got a cursor-intangible element: redisplay will move point to > a visible (and intangible) part of the buffer, then run p-r-f which > moves point outside of the window, after which redisplay has two > choices: either it decides to scroll to where point is (which would be > wrong, since we've just scrolled so we should move point rather than > scroll), or it moves point back into the intangible element. Unless the functions in the hooks continues to change the display this can't loop, or can it?