From: Bill White <billw@wolfram.com>
Cc: ding@gnus.org
Subject: Re: What coding system to use for .spam-stat.el
Date: Thu, 23 Jan 2003 08:37:05 -0600 [thread overview]
Message-ID: <ruon0lsrkz2.fsf@billwlx.wolfram.com> (raw)
In-Reply-To: <xiulm1cc9z0.fsf@pcniklas.axis.se> (Niklas Morberg's message of "Thu, 23 Jan 2003 13:43:47 +0100")
On Thu Jan 23 2003 at 06:43, Niklas Morberg <niklas.morberg@axis.com> said:
> For some reason, I now get asked the question:
>
> No default coding systems to try.
> Select one of the following safe coding systems:
> ...
>
> every time I exit a spam or ham group. I've tried choosing
> emacs-mule, but the setting doesn't "stick", so I get asked the same
> question over and over again.
It's just an elisp file - have you tried a local variable?
At the bottom of the file:
; Local Variables: ***
; coding:sjis ***
; End: ***
or at the top:
;-*- coding: utf-8; -*-
I suppose the string you want would be "emacs-mule" rather than "sjis"
Cheers -
bw
--
Bill White . billw@wolfram.com . http://members.wri.com/billw
"No ma'am, we're musicians."
next prev parent reply other threads:[~2003-01-23 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 12:43 Niklas Morberg
2003-01-23 14:37 ` Bill White [this message]
2003-01-23 20:14 ` Alex Schroeder
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=ruon0lsrkz2.fsf@billwlx.wolfram.com \
--to=billw@wolfram.com \
--cc=ding@gnus.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.
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).