From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: Documentation of transient-mark-mode is sloppy, wrong, and confused. Date: Tue, 02 Jun 2009 20:50:33 +0900 Message-ID: <87fxeij1me.fsf@uwakimon.sk.tsukuba.ac.jp> References: <20090528122927.GA2175@muc.de> <87fxepf9s8.fsf@cyd.mit.edu> <20090528201529.GA4605@muc.de> <87bppdx8c0.fsf@cyd.mit.edu> <20090528230359.GA1474@muc.de> <4A1F7706.80501@online.de> <878wkgco3b.fsf@uwakimon.sk.tsukuba.ac.jp> <20090529085852.GA2793@muc.de> <87vdngbs1w.fsf@uwakimon.sk.tsukuba.ac.jp> <4A24C571.4070300@online.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1243943226 9994 80.91.229.12 (2 Jun 2009 11:47:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 2 Jun 2009 11:47:06 +0000 (UTC) Cc: Alan Mackenzie , Kevin Rodgers , Stefan Monnier , emacs-devel@gnu.org To: Andreas Roehler Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 02 13:47:02 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MBSSK-0006fM-NS for ged-emacs-devel@m.gmane.org; Tue, 02 Jun 2009 13:47:01 +0200 Original-Received: from localhost ([127.0.0.1]:39646 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MBSSK-0005RX-8f for ged-emacs-devel@m.gmane.org; Tue, 02 Jun 2009 07:47:00 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MBSSF-0005RE-D9 for emacs-devel@gnu.org; Tue, 02 Jun 2009 07:46:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MBSSA-0005Qe-Ig for emacs-devel@gnu.org; Tue, 02 Jun 2009 07:46:54 -0400 Original-Received: from [199.232.76.173] (port=49462 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MBSSA-0005QX-EJ for emacs-devel@gnu.org; Tue, 02 Jun 2009 07:46:50 -0400 Original-Received: from mtps02.sk.tsukuba.ac.jp ([130.158.97.224]:39539) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MBSS9-0003AR-Of for emacs-devel@gnu.org; Tue, 02 Jun 2009 07:46:50 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mtps02.sk.tsukuba.ac.jp (Postfix) with ESMTP id 6A198820E; Tue, 2 Jun 2009 20:46:43 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 9F7381A2645; Tue, 2 Jun 2009 20:50:33 +0900 (JST) In-Reply-To: <4A24C571.4070300@online.de> X-Mailer: VM 8.0.12-devo-585 under 21.5 (beta28) "fuki" 83e35df20028+ XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:111281 Archived-At: Andreas Roehler writes: > AFAIU definitions (including zmacs-regions) are here intermixed. At > least one may be dropped. I don't think so. zmacs-regions is a variable that controls a feature. Some people dislike that feature, so it is a user option. The other two are functions that retrieve internal state. None of the three can be defined in terms of the others without changing the semantics radically. > For me GNU variable `mark-active' is more straightforward by its value, > but should be named `mark-set' rather. What do you need it to do that plain `mark' doesn't already do? Note that since all of these APIs are of long standing in XEmacs at least, I'm pretty sure they're not going to change in XEmacs, despite the sheer perversity of the current semantics of `region-exists-p', `region-active-p', and `mark'. But it would be reasonable to add new ones if there are things that can't be easily done with the current ones, or if it would make code clearer.