From: Deniz Dogan <deniz.a.m.dogan@gmail.com>
To: kovvalsky <fibo.kowalsky@gmail.com>
Cc: Help-gnu-emacs@gnu.org
Subject: Re: Specify file encoding when storing a plain text or a source code
Date: Tue, 1 Feb 2011 05:37:59 +0100 [thread overview]
Message-ID: <AANLkTi=bj=1=s5-9tnDMtFn3u-geN6piKA3HmkYWe83u@mail.gmail.com> (raw)
In-Reply-To: <30811936.post@talk.nabble.com>
2011/2/1 kovvalsky <fibo.kowalsky@gmail.com>:
>
> How do you specify file encoding when storing a plain text or a source code
> in emacs?
> -
> thank you in advance.
> --
> View this message in context: http://old.nabble.com/Specify-file-encoding-when-storing-a-plain-text-or-a-source-code-tp30811936p30811936.html
> Sent from the Emacs - Help mailing list archive at Nabble.com.
>
You can use "C-x RET f" (set-buffer-file-coding-system).
If CODING-SYSTEM leaves the text conversion unspecified, or if it leaves
the end-of-line conversion unspecified, FORCE controls what to do.
If FORCE is nil, get the unspecified aspect (or aspects) from the buffer's
previous `buffer-file-coding-system' value (if it is specified there).
Otherwise, leave it unspecified.
This marks the buffer modified so that the succeeding C-t C-s
surely saves the buffer with CODING-SYSTEM. From a program, if you
don't want to mark the buffer modified, specify t for NOMODIFY.
If you know exactly what coding system you want to use,
just set the variable `buffer-file-coding-system' directly.
--
Deniz Dogan
next prev parent reply other threads:[~2011-02-01 4:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 23:33 Specify file encoding when storing a plain text or a source code kovvalsky
2011-02-01 4:37 ` Deniz Dogan [this message]
2011-02-01 10:09 ` kovvalsky
2011-02-01 5:56 ` Eli Zaretskii
2011-02-01 10:12 ` kovvalsky
2011-02-01 11:26 ` Peter Dyballa
2011-02-01 13:00 ` Eli Zaretskii
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='AANLkTi=bj=1=s5-9tnDMtFn3u-geN6piKA3HmkYWe83u@mail.gmail.com' \
--to=deniz.a.m.dogan@gmail.com \
--cc=Help-gnu-emacs@gnu.org \
--cc=fibo.kowalsky@gmail.com \
/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.