all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Still problems with desktop.el -> coding
Date: Wed, 5 Jul 2006 14:07:22 +0200	[thread overview]
Message-ID: <85774AF7-CE2D-4F58-B817-F20A69519865@Web.DE> (raw)
In-Reply-To: <200607051344.54702.sebastianmeisel@web.de>


Am 05.07.2006 um 13:44 schrieb Sebastian Meisel:

>>
>> You might like to add to .emacs:
>>
>> 	(prefer-coding-system          'iso-latin-1-unix)
>>
> No change.
>
>>
>> Another cure is a header line like this:
>>
>> 	%%% -*- mode: LaTeX-mode; coding: iso-8859-15-unix; fill-column:  
>> 90 -*-
>
> No change.
>
>> 	%
>> 	% Local Variables:
>> 	% mode: LaTeX
>> 	% fill-column: 160
>> 	% coding-system: iso-latin-9
>> 	% End:
>> 	%
>> 	%%
>
> It all doesn't help.

I didn't mention it explicitly: the ``™´´ characters won't go away  
automatically -- who or what has the capacity to find they're wrong  
there? You'll have to delete them first. And if desktop re-opens  
them, then it can't happen that the local variables get overridden  
and they are inserted again.

Before and after you've saved the corrected versions, take a look at  
mode-line! What characters are used to describe the recent buffer's  
encoding? (They're the first ones in that line, up to ``:´´ usually.)

Could you also ask the Gentoo folks what they thought was an  
advantage for GNU Emacs 21.4 on Gentoo Linux? Some OS vendors have  
very special thoughts ...

--
Mit friedvollen Grüßen

   Pete

Alle reden vom Wetter - die Bahn fährt nicht.

  reply	other threads:[~2006-07-05 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05  9:32 Still problems with desktop.el -> coding Sebastian Meisel
2006-07-05 10:56 ` Peter Dyballa
2006-07-05 11:44   ` Sebastian Meisel
2006-07-05 12:07     ` Peter Dyballa [this message]
2006-07-05 15:17     ` Solved: " Sebastian Meisel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85774AF7-CE2D-4F58-B817-F20A69519865@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.