From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "dsoliver@earthlink.net" Newsgroups: gmane.emacs.help Subject: Re: gnu/emacs 2.4 in and out of X Date: 29 Aug 2006 22:11:51 -0700 Organization: http://groups.google.com Message-ID: <1156914710.967714.114610@b28g2000cwb.googlegroups.com> References: <1156813964.346874.293340@74g2000cwt.googlegroups.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: sea.gmane.org 1156916485 11244 80.91.229.2 (30 Aug 2006 05:41:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 30 Aug 2006 05:41:25 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Aug 30 07:41:24 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GIIpH-0002hV-3N for geh-help-gnu-emacs@m.gmane.org; Wed, 30 Aug 2006 07:41:23 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GIIpG-0006KP-IE for geh-help-gnu-emacs@m.gmane.org; Wed, 30 Aug 2006 01:41:22 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews.google.com!b28g2000cwb.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 48 Original-NNTP-Posting-Host: 24.180.52.62 Original-X-Trace: posting.google.com 1156914714 9531 127.0.0.1 (30 Aug 2006 05:11:54 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Wed, 30 Aug 2006 05:11:54 +0000 (UTC) In-Reply-To: User-Agent: G2/0.2 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5,gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: b28g2000cwb.googlegroups.com; posting-host=24.180.52.62; posting-account=Mu7y7gwAAAADJ71fYmB0mt2IqYzXiLJh Original-Xref: shelby.stanford.edu gnu.emacs.help:141435 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:37055 Archived-At: Peter Dyballa wrote: > Am 29.08.2006 um 03:12 schrieb dsoliver@earthlink.net: > > > Esperanto Post-fix > > You could try to use in those file a header line like > > -*- mode: text; coding: iso-8859-3; -*- > > or use a set of buffer-local variable settings like these at the end > of the file > > %%% Local Variables: > %%% mode: text > %%% coding: iso-8859-3 > %%% End: > > The menus Options -> Mule -> Set Coding Systems could allow > exceptions from UTF-8. > > There are variables you could set: > > default-buffer-file-coding-system > file-coding-system-alist > > The latter could make files with a particular extension be iso-8859-3 > by default. > Thanks, Pete. I tried all of these things and it still doesn't work. Once again the problem is that I can work fine in Esperanto while in console mode not in X. I now can do the same in X. I added the iso-8859-3 font to my .Xresources file. However, my main problem still remains. When I leave X and return to the console, emacs no longer can read any of my files with iso-8858-3 characters. The mode line looks the same as before I started X, but emacs no longer understands those modes. I go through the actions of setting up things again. It doesn't work. I then start X again and things work again. I stop X, things don't work. So the problem is that when I start X after I have been successfully working on Esperanto files, I reach a point of no return with regard to emacs and my run level 3 text console. Emacs appears to be suddenly broken; I return to X and emacs works again as though nothing happened. To get my text console to work again, I have to reboot. I've looked at various logs, but I can't find what is going on. Thanks again for your help.