From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Alex Newsgroups: gmane.emacs.bugs Subject: bug#20253: 24.4; Document `region' face behavior changes, overlay, priority Date: Wed, 21 Sep 2016 13:10:43 -0600 Message-ID: <87r38dnk5o.fsf@gmail.com> References: <0ad651bb-89bc-4e86-9354-063db1c400a2@default>> <87inu2vx36.fsf@gmail.com>> <83k2eh9ic9.fsf@gnu.org>> <83wpih7ynm.fsf@gnu.org> <87vaxpnmwz.fsf@gmail.com> <834m59f6ds.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1474485112 25355 195.159.176.226 (21 Sep 2016 19:11:52 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 21 Sep 2016 19:11:52 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) Cc: 20253@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Sep 21 21:11:48 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bmmvf-0004uc-Pr for geb-bug-gnu-emacs@m.gmane.org; Wed, 21 Sep 2016 21:11:36 +0200 Original-Received: from localhost ([::1]:51154 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmmvh-0005N6-3l for geb-bug-gnu-emacs@m.gmane.org; Wed, 21 Sep 2016 15:11:37 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47372) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmmvF-00058M-5W for bug-gnu-emacs@gnu.org; Wed, 21 Sep 2016 15:11:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bmmv8-0003a9-Qd for bug-gnu-emacs@gnu.org; Wed, 21 Sep 2016 15:11:08 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:53738) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmmv8-0003a2-M1 for bug-gnu-emacs@gnu.org; Wed, 21 Sep 2016 15:11:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bmmv8-0002uI-IE for bug-gnu-emacs@gnu.org; Wed, 21 Sep 2016 15:11:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Alex Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 21 Sep 2016 19:11:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20253 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 20253-submit@debbugs.gnu.org id=B20253.147448505611161 (code B ref 20253); Wed, 21 Sep 2016 19:11:02 +0000 Original-Received: (at 20253) by debbugs.gnu.org; 21 Sep 2016 19:10:56 +0000 Original-Received: from localhost ([127.0.0.1]:59928 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bmmv2-0002tx-6j for submit@debbugs.gnu.org; Wed, 21 Sep 2016 15:10:56 -0400 Original-Received: from mail-it0-f53.google.com ([209.85.214.53]:35890) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bmmuy-0002tj-0r for 20253@debbugs.gnu.org; Wed, 21 Sep 2016 15:10:55 -0400 Original-Received: by mail-it0-f53.google.com with SMTP id o3so136857081ita.1 for <20253@debbugs.gnu.org>; Wed, 21 Sep 2016 12:10:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=yVxukZ+MIyhM0GYXvaIiK1VS4Wzre+VjC26TCWvXB4I=; b=VrrXjofgoi2QNF8gm52I0/LTk9IhVQ0PORznR8+Pyv0zGjm6uionAt75yAu8fT+CBg 3H9Dlinu4FOQ48VFaXQq+S8gMzP7iKLCv2e0KgAVGxffeawjWILQQ9eLMn/6uWAIcLYi LXyz5/io9gvK7FC2eO+PSoXR2yzjXcss1z+mes2FSQKAd7fNVfzalJVOJFny8Fl1ZYYW df+fwhIKeqmuyHIR7b1l8QXjcgc/SNPJ0TMzrl9eaXO33hYVS22sPg2oct3voIZ1x4p4 unQ4uvLfwfrXSEOq9yAepe1TDTcMcNE5jYW62NC1t8k3J+uMhqslip0CYquzkBnJafOQ VvNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=yVxukZ+MIyhM0GYXvaIiK1VS4Wzre+VjC26TCWvXB4I=; b=Hq99/Qq5vxwbDx6F9V33GuAXxyLdNdIktr+v5ZdJxNpg8dKX5LBZe3EQTn6nBDPF0/ jGqwA6yWjSsUAhkv6PE4nImJW0pRVrLEqKOC70X4ikPuwL/djqQNdGgZYl/Uzj63Nc3v YmLS/Ab3Q7x02jIpcs41dhEB14cDJVx5qZsRpAR/R2ylxvEBAHBtzwkVhW01hjZk++S0 U5SLgcUnVAJ5z23DcEf3Mmjxu7XrucWI1IOqUXOrmb6i5b0JKhJTjWWlt/WQ4IMIugZk FJLS/iq9sqjT3vfHciZnkn4/r20MSIC42vRCt0Jnt4BLr2pUWux2WVTievWPCgtLK50I n7Yw== X-Gm-Message-State: AE9vXwMjCog29Xu7hrcJL1h8GGUgGWFU1HAgsKY9bZtOpxxy5wxL3N6qmiDIjSV4hRIzOw== X-Received: by 10.36.73.19 with SMTP id z19mr6496215ita.36.1474485046450; Wed, 21 Sep 2016 12:10:46 -0700 (PDT) Original-Received: from lylat (S01061859339e9903.ss.shawcable.net. [174.2.107.88]) by smtp.gmail.com with ESMTPSA id v69sm12721939itc.1.2016.09.21.12.10.45 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 21 Sep 2016 12:10:46 -0700 (PDT) In-Reply-To: <834m59f6ds.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 21 Sep 2016 21:35:27 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:123529 Archived-At: Eli Zaretskii writes: >> From: Alex >> Cc: Drew Adams , 20253@debbugs.gnu.org >> Date: Wed, 21 Sep 2016 12:11:08 -0600 >> >> My curiosity about the meaning of a cons cell priority is what pushed me >> to find and respond to this bug, so I guess that would count as one >> question. >> >> Since the region overlay is a very common overlay, I think it is >> important enough to at least have a passing statement about its priority >> value type in the documentation. Even something like "For example, some >> overlays use a cons cell priority (PRIMARY . SECONDARY), where SECONDARY >> is used as a tie-breaker if the PRIMARY priorities and boundaries of the >> overlays are equal." would be nice. > > I hoped to hear some practical reasons for this, not just curiosity. > Like practical use cases where knowing that internal detail (as > opposed to using the documented methods of comparing priorities etc.) > is imperative for that use case. I should have mentioned that aside from curiosity I did need to know about what the region overlay's priority represented so that I can know what priority to give overlays that interacted with the region overlay. > People often ask questions here out of curiosity about the display > engine's inner workings, for example, and I try to answer them as best > as I can. But that doesn't mean all I write here in those discussions > should be in the manual. Right, but I think that the region overlay is prominent enough to have all of its properties be in a documented form. > IOW, the need to have some internal detail described in the manual > (which implies we will have to update and maintain it for the years to > come) should have more important reasons than just curiosity. Hopefully the above is enough to warrant an extra sentence or two in the manual.