From: Shaun Lipscombe <shaun.lipscombe@gasops.co.uk>
Subject: Warning
Date: 05 Feb 1999 10:33:05 +0000 [thread overview]
Message-ID: <wkk8xx16ou.fsf@mail.gasops.co.uk> (raw)
When 'q''ing the Summary buffer I am presented (occasionaly) with a
Warning buffer the contents of which are displayed here:
The target text contains the following non ASCII characters(s):
latin-iso8859-1: e
These can't be encoded safely by the following safe coding systems:
iso-8859-1 iso-2022-7bit iso2022-7bit-lock iso2022-8bit-ss2
emacs-mule raw-text iso-2022-7bit-ss2 compound-text
The mini-buffer states:
Select coding system (default iso-8859-1):
To which I just hit enter. What is this, have I screwed something up?
--
( )
~oo~
.. Gnu!
/ =\ \=
- - -
next reply other threads:[~1999-02-05 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-05 10:33 Shaun Lipscombe [this message]
1999-02-05 13:46 ` Warning Jack Vinson
1999-02-05 14:52 ` Warning Shaun Lipscombe
1999-02-09 15:25 ` Warning Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
1998-11-07 13:58 Warning Lars Magne Ingebrigtsen
1998-11-09 16:39 ` Warning Wes Hardaker
1998-11-09 16:40 ` Warning Wes Hardaker
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=wkk8xx16ou.fsf@mail.gasops.co.uk \
--to=shaun.lipscombe@gasops.co.uk \
/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 NNTP newsgroup(s).