From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: region-active-p et al Date: Mon, 02 Jan 2017 17:33:53 +0200 Message-ID: <83pok5fpcu.fsf@gnu.org> References: <63474c32-666d-dc16-d5de-98164172fb71@online.de> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1483371302 16014 195.159.176.226 (2 Jan 2017 15:35:02 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 2 Jan 2017 15:35:02 +0000 (UTC) Cc: emacs-devel@gnu.org To: Andreas =?utf-8?Q?R=C3=B6hler?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 02 16:34:58 2017 Return-path: Envelope-to: ged-emacs-devel@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 1cO4dT-0003PG-Mw for ged-emacs-devel@m.gmane.org; Mon, 02 Jan 2017 16:34:55 +0100 Original-Received: from localhost ([::1]:57399 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cO4dX-0003ko-Pr for ged-emacs-devel@m.gmane.org; Mon, 02 Jan 2017 10:34:59 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39017) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cO4cP-0003ie-Rk for emacs-devel@gnu.org; Mon, 02 Jan 2017 10:33:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cO4cM-0004Zv-Nv for emacs-devel@gnu.org; Mon, 02 Jan 2017 10:33:49 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39611) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cO4cM-0004Zl-Ln; Mon, 02 Jan 2017 10:33:46 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4413 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cO4cL-0006iL-HI; Mon, 02 Jan 2017 10:33:46 -0500 In-reply-to: <63474c32-666d-dc16-d5de-98164172fb71@online.de> (message from Andreas =?utf-8?Q?R=C3=B6hler?= on Mon, 2 Jan 2017 12:50:35 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:211066 Archived-At: > From: Andreas Röhler > Date: Mon, 2 Jan 2017 12:50:35 +0100 > > Happy new year! And the same to you. > Got a bug-report at > https://gitlab.com/python-mode-devs/python-mode/issues/27 which points > me at a quirk in region-active-p: > > Questioning transient-mark-mode does not belong here. It's a > user/convenience thing whilst > region-active-p is a core thing. Actually, both region-active-p and use-region-p are explicitly documented to pay attention to transient-mark-mode. These two functions exist to allow applications to change their behavior when an active region (not just any region) exists. If python-mode wants to act on region regardless of transient-mark-mode, it should look at the mark, and not use these two functions. They are not meant for that use case.