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: colon in the mode-line Date: Thu, 30 Nov 2006 00:05:35 +0100 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1164841574 5464 80.91.229.2 (29 Nov 2006 23:06:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 29 Nov 2006 23:06:14 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 30 00:06:11 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GpYV6-0000cX-0s for ged-emacs-devel@m.gmane.org; Thu, 30 Nov 2006 00:06:00 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GpYV5-0003Xj-CA for ged-emacs-devel@m.gmane.org; Wed, 29 Nov 2006 18:05:59 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GpYUm-0003UZ-5S for emacs-devel@gnu.org; Wed, 29 Nov 2006 18:05:40 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GpYUj-0003Sx-KI for emacs-devel@gnu.org; Wed, 29 Nov 2006 18:05:39 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GpYUj-0003SY-7A for emacs-devel@gnu.org; Wed, 29 Nov 2006 18:05:37 -0500 Original-Received: from [66.249.92.172] (helo=ug-out-1314.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GpYUi-0002UZ-Oj for emacs-devel@gnu.org; Wed, 29 Nov 2006 18:05:36 -0500 Original-Received: by ug-out-1314.google.com with SMTP id j3so2112716ugf for ; Wed, 29 Nov 2006 15:05:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LHv6OD2zWvgHA9P5xKGNzgspThoevAgTaEihLxp5CuxszOwfFmFC1f//eU2oelY3sZhTJnwrlwm0l/D42SHkqd4AwcqOb+57Wgdynb1deh3I9kywQlnnGclwtDqqwX3vpPizy2ixdPxMMhgEk4KuDHqI4MkfDXYbY2w0eHvl12U= Original-Received: by 10.82.127.15 with SMTP id z15mr706607buc.1164841535707; Wed, 29 Nov 2006 15:05:35 -0800 (PST) Original-Received: by 10.82.147.2 with HTTP; Wed, 29 Nov 2006 15:05:35 -0800 (PST) Original-To: "Eli Zaretskii" In-Reply-To: Content-Disposition: inline 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:63084 Archived-At: On 11/29/06, Eli Zaretskii wrote: > If the buffer's file uses > carriage-return linefeed, the colon changes to either a backslash > (@samp{\}) or @samp{(DOS)}, depending on the operating system. If the > file uses just carriage-return, the colon indicator changes to either > a forward slash (@samp{/}) or @samp{(Mac)}. On some systems, Emacs > displays @samp{(Unix)} instead of the colon for files that use newline > as the line separator. That's entirely my point: the description of multibyte character support confusingly refers to a colon that some users won't ever see. It would be better to simply refer to the first (or leftmost, whatever) chars of the mode line, instead of them being "before the colon". /L/e/k/t/u