From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: The future of Follow Mode - a proposal. Date: Wed, 24 Feb 2016 19:30:55 -0500 Message-ID: References: <20160218195630.GA2697@acm.fritz.box> <837fi1u5qt.fsf@gnu.org> <20160219142522.GA3193@acm.fritz.box> <83povsr8cc.fsf@gnu.org> <20160219181834.GC3193@acm.fritz.box> <83io1kr12k.fsf@gnu.org> <20160220124415.GA1758@acm.fritz.box> <83wppzo7lf.fsf@gnu.org> <20160223231156.GA26899@acm.fritz.box> <83a8mqhvym.fsf@gnu.org> <837fhthq5z.fsf@gnu.org> <834mcxhnaq.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1456360286 15297 80.91.229.3 (25 Feb 2016 00:31:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Feb 2016 00:31:26 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 25 01:31:17 2016 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 1aYjps-0001Gj-BW for ged-emacs-devel@m.gmane.org; Thu, 25 Feb 2016 01:31:16 +0100 Original-Received: from localhost ([::1]:39255 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYjpr-0001CS-TY for ged-emacs-devel@m.gmane.org; Wed, 24 Feb 2016 19:31:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40771) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYjpf-0001CI-65 for emacs-devel@gnu.org; Wed, 24 Feb 2016 19:31:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYjpe-0003nD-Cl for emacs-devel@gnu.org; Wed, 24 Feb 2016 19:31:03 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:4711) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYjpZ-0003k5-PG; Wed, 24 Feb 2016 19:30:57 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0A2FgA731xV/+OhCkxcgxCEAoVVwwsEAgKBPDwRAQEBAQEBAYEKQQWDXQEBAwFWIwULCzQSFBgNJIg3CM8jAQEBBwEBAQEeizqFBQeELQWMMI09hSqSFIIUgUUjgWaCMCCCeAEBAQ X-IPAS-Result: A0A2FgA731xV/+OhCkxcgxCEAoVVwwsEAgKBPDwRAQEBAQEBAYEKQQWDXQEBAwFWIwULCzQSFBgNJIg3CM8jAQEBBwEBAQEeizqFBQeELQWMMI09hSqSFIIUgUUjgWaCMCCCeAEBAQ X-IronPort-AV: E=Sophos;i="5.13,465,1427774400"; d="scan'208";a="194312209" Original-Received: from 76-10-161-227.dsl.teksavvy.com (HELO pastel.home) ([76.10.161.227]) by ironport2-out.teksavvy.com with ESMTP; 24 Feb 2016 19:30:55 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 590C760420; Wed, 24 Feb 2016 19:30:55 -0500 (EST) In-Reply-To: <834mcxhnaq.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 24 Feb 2016 22:21:33 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 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:200645 Archived-At: > The most striking one is vertical-motion (which doesn't belong to > redisplay at all, and thus will not benefit from your suggestion). > Redisplay proper does similar stuff at places as part of its decision > where to place point and whether/by how much to scroll the window in > order to bring point back into view. I see, thanks. Indeed both examples fall outside the scope of "redisplay" that could be covered by the kind of hook I have in mind. I live in a world where wrapped lines are sufficiently rare that I don't really care and rarely think about what can happen in those cases. But now that I think about it: I'm not sure how vertical-motion could handle a "multiple-window" case where the windows don't have the same width (same thing in other similar cases, such as with overlays with a `window' property that make them only apply to some of the multiple windows, or when the windows aren't all in the same frame and don't use the same font). The desired semantic seems undefined except for the case where the vertical motion is applied to the "currently displayed state" (so we know when to use which window data). Stefan