From: Sharon Kimble <boudiccas@skimble.plus.com>
To: tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org
Subject: Re: \201\236 appearing in emacs.desktop
Date: Sat, 08 Jul 2017 18:02:59 +0100 [thread overview]
Message-ID: <87eftq7tfg.fsf@skimble.plus.com> (raw)
In-Reply-To: <20170708152050.GB29492@tuxteam.de> (tomas@tuxteam.de's message of "Sat, 8 Jul 2017 17:20:50 +0200")
[-- Attachment #1: Type: text/plain, Size: 2256 bytes --]
tomas@tuxteam.de writes:
> On Sat, Jul 08, 2017 at 01:23:22PM +0100, Sharon Kimble wrote:
>> <tomas@tuxteam.de> writes:
>>
>> > On Sat, Jul 08, 2017 at 09:46:27AM +0100, Sharon Kimble wrote:
>> >>
>> >> I've a problem that seems to have only developed this morning with my
>> >> 'emacs.desktop' file [...]
>
> [...]
>
>> I think that this is the answer to what you're saying -
>>
>> --8<---------------cut here---------------start------------->8---
>> Coding system for saving this buffer:
>> U -- utf-8-unix (alias: mule-utf-8-unix)
> [...]
>> --8<---------------cut here---------------end--------------->8---
>
> Pretty unsurprising. Sorry I can't say where those \201\236 are
> coming from. Emacs is able to transparently represent "byte values"
> which would be an encoding error within an otherwise UTF-8 encoded
> buffer (actually it uses an extension of UTF-8 for that). To display
> that, it resorts to those octal escapes, \nnn.
>
> But no idea how they got in in the first place.
>
> What happens if you delete them? Do they reappear next time around?
Thanks Tomas.
Yes. The only way round it that I've found is once 'emacs.desktop' gets
corrupted like that is to delete it and then rebuild my previous opened
buffers from memory.
>
>> And my sig is correct, I am running these setups.
>
> Civilised :-)
>
>> And thinking about it, these are all settings relating to utf-8 in my
>> config file -
>
> [...]
>
>> I've separated the separate c ode blocks using #'s. Is it possible that
>> all of those could be causing my problem? And if so, what can I chop out
>> and yet still retain utf-8 working?
>
> They all look pretty harmless to me. Actually they should be mostly
> unnecessary, since the defaults should work more or less like that
> (but note that I may well have missed some detail!).
>
And now that I've been looking at all my old 'emacs.desktop' files, I
can't find any where its corrupted, so it seems to have corrected itself
this time. For a while at least.
Thanks
Sharon.
--
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk
Debian 9.0, fluxbox 1.3.5-2, emacs 25.1.1, org-mode 9.0.9
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-07-08 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 8:46 \201\236 appearing in emacs.desktop Sharon Kimble
2017-07-08 11:19 ` tomas
2017-07-08 12:23 ` Sharon Kimble
2017-07-08 15:20 ` tomas
2017-07-08 15:29 ` Eli Zaretskii
2017-07-08 17:02 ` Sharon Kimble [this message]
2017-07-09 9:56 ` tomas
2017-07-09 16:49 ` Sharon Kimble
2017-07-09 19:48 ` tomas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eftq7tfg.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).