From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Customizing default-buffer-file-coding-system
Date: Wed, 30 Jul 2003 16:01:35 +0200 [thread overview]
Message-ID: <84u1946rls.fsf@slowfox.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 1fyvovy.76ses030yfcyN%aaron@avalon.pascal-central.com
aaron@avalon.pascal-central.com (Aaron Davies) writes:
> Thanks, but I'm not sure those have anything to do with what I want.
> They seem to be ways to specify the coding system to use when reading
> existing files; I want to specify the coding system for new files.
default-buffer-file-coding-system seems to be the right variable.
Its documentation points to buffer-file-coding-system which states
that the value is used for writing.
--
~/.signature
next prev parent reply other threads:[~2003-07-30 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 22:56 Customizing default-buffer-file-coding-system Aaron Davies
2003-07-29 23:13 ` martin
2003-07-30 2:56 ` Aaron Davies
2003-07-30 14:01 ` Kai Großjohann [this message]
2003-07-30 5:51 ` Eli Zaretskii
[not found] ` <mailman.694.1059540868.8231.help-gnu-emacs@gnu.org>
2003-07-30 19:45 ` Aaron Davies
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=84u1946rls.fsf@slowfox.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).