From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Ellispes is not in utf-8? Date: Thu, 23 Dec 2010 03:38:17 +0100 Message-ID: References: <4D12B368.2010300@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1293071991 26159 80.91.229.12 (23 Dec 2010 02:39:51 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 23 Dec 2010 02:39:51 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 23 03:39:47 2010 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.69) (envelope-from ) id 1PVb4v-0004BM-A2 for ged-emacs-devel@m.gmane.org; Thu, 23 Dec 2010 03:39:45 +0100 Original-Received: from localhost ([127.0.0.1]:42721 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PVb4o-0005fy-Nb for ged-emacs-devel@m.gmane.org; Wed, 22 Dec 2010 21:38:46 -0500 Original-Received: from [140.186.70.92] (port=34683 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PVb4j-0005fm-9R for emacs-devel@gnu.org; Wed, 22 Dec 2010 21:38:42 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PVb4h-0007l0-ED for emacs-devel@gnu.org; Wed, 22 Dec 2010 21:38:40 -0500 Original-Received: from mail-ew0-f41.google.com ([209.85.215.41]:54997) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PVb4h-0007kq-8g; Wed, 22 Dec 2010 21:38:39 -0500 Original-Received: by ewy27 with SMTP id 27so4047318ewy.0 for ; Wed, 22 Dec 2010 18:38:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=mteaYZhmx+outSepw53CeMjfewhjM4PWhvwRaxyscdw=; b=is/blOXGCB6JzblqZFbQhMNeJJaQqwmQZ3X5h8cgpvvFz36FMpsL5xu2z4zDW0mOQn +VA0SdDWzR7BEql2QwbWWjF30n5zITXPhIDqmilzcca+oftVhI/SxOILmnp+KuLYp+yA cxsGpBFfzXAYo1EPI7KgHwJOLXntOgNx+/RTA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=kDMBetjjLuNdHnkYV14/4qotIDc3EEsNwSy3SEi5gCXM5CPu868+r4Du2J/H1EYs1Z Qs2CMuqHa8dbZRVz3y7a7NSOyg+ymPV5fQ6W7rtrayyRXusvW103aFDA0z+T3nIaNBBW tReKwsFAlBq6RdjvAz/2g5CKngrItUHgUjgfY= Original-Received: by 10.213.35.209 with SMTP id q17mr6219465ebd.97.1293071917795; Wed, 22 Dec 2010 18:38:37 -0800 (PST) Original-Received: by 10.213.20.148 with HTTP; Wed, 22 Dec 2010 18:38:17 -0800 (PST) In-Reply-To: <4D12B368.2010300@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) 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:133913 Archived-At: On Thu, Dec 23, 2010 at 3:26 AM, Jason Rumney wrote: > On 23/12/2010 09:47, Lennart Borgman wrote: >> >> I just copied ellipses from this page: >> >> =C2=A0 http://en.wikipedia.org/wiki/Ellipsis >> >> and inserted them (with cua-paste) in a ruby file. At the end of this >> file I added: >> >> # Local variables: >> # coding: utf-8 >> # End: >> >> > > This seems to be a bug in ruby-mode. It has a feature that automatically > inserts a coding header to the start of the file, which is enabled by > default. However, this does not respect the manual setting that you made = in > the buffer - nor does it respect any changes you make to the header that = it > has inserted. =C2=A0It seems you are forced to use C-x RET f to set the > coding-system if you want ruby-mode to respect your request. Thanks, I see. What do we do to get this fixed?