From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: display.texi: (,) isn't documented. Date: Thu, 7 Jun 2007 19:42:14 +0200 Message-ID: References: <87y7ivkago.fsf@debby.local.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1181238143 32730 80.91.229.12 (7 Jun 2007 17:42:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 7 Jun 2007 17:42:23 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 07 19:42:21 2007 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 1HwM04-000138-Rr for ged-emacs-devel@m.gmane.org; Thu, 07 Jun 2007 19:42:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HwM04-00016W-Bg for ged-emacs-devel@m.gmane.org; Thu, 07 Jun 2007 13:42:20 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HwM01-00016R-Kl for emacs-devel@gnu.org; Thu, 07 Jun 2007 13:42:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HwLzz-00014C-TV for emacs-devel@gnu.org; Thu, 07 Jun 2007 13:42:17 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HwLzz-00013x-Oy for emacs-devel@gnu.org; Thu, 07 Jun 2007 13:42:15 -0400 Original-Received: from wx-out-0506.google.com ([66.249.82.227]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HwLzz-0006Y8-CG for emacs-devel@gnu.org; Thu, 07 Jun 2007 13:42:15 -0400 Original-Received: by wx-out-0506.google.com with SMTP id h26so496575wxd for ; Thu, 07 Jun 2007 10:42:14 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GGL6C9+a22xzN9kBaeF188GhSpLtvLMtnDRM6bFsCGtM89UpksYqY7Pm+tMzQpFSRwt4Z7Q5Yykzu4eG51JKz/WAD3sIwa4idkI7Th/0dadVhleIGVdWB85prv+0cd4fFHTlJTYNJLtDAvQpVJyT5jelAu9np/uGV3Ro+7BM0JE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hupZdeMlmuRwgbFjgnplGY8NJIGJ8punPBOCw77siV4hJNenAPyEB1uO4jT7+sZt1VPULZP8RZXHSgLrEM4zv7EvqBJJd2SvLIU5h1TYjQB1aFwTLKoTfUCXQxd7Aq6NaCxbtZ8gjKib7DmI+VPoJ3sZYD24sPxPavyGqiJgYW0= Original-Received: by 10.90.104.14 with SMTP id b14mr1895191agc.1181238134528; Thu, 07 Jun 2007 10:42:14 -0700 (PDT) Original-Received: by 10.90.103.8 with HTTP; Thu, 7 Jun 2007 10:42:14 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-detected-kernel: Linux 2.4-2.6 (Google crawlbot) 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:72428 Archived-At: On 6/7/07, Drew Adams wrote: > Some people have said that it is obvious that line comes before column. I > don't see why that's obvious As Lennart and others have explained, because it is customary to refer first to more important things, and lines are more fundamental when dealing with an Emacs buffer than columns. It is a bigger movement to advance a line than a column. line-number-mode is enabled by default, column-number-mode is not. > 12:25 can be confused with a time. 12-25 can be confused with a range of > some kind (12 through 25). 12.25 can be confused with a decimal number. 12/25 can be confused with? A rational number? :) > Uppercase letters such as L and C are hard to separate visually from the > digits. Using l and c risks confusion between l and 1. Use "r" (for rows) and "c". 25r32c is still horrible, though. > In a buffer, horizontal and vertical positions > can only mean lines and columns, however (unless one is thinking pixels). That is true, but it doesn't mean that going from x,y to row,column (or column,row :) is intuitive at all. > It's true that y suggests increasing values toward the top, but practice > would soon put the lie to that association. That's true for every format described in this tread, even the "Ln vs. Cn vs. (l,c)" style that we have now. > but I can live with any of the > proposals, including what we have now. Same here. I won't be using it anyway. Juanma