unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: specifying coding system on the first/second line
Date: Tue, 11 Oct 2005 19:28:13 +0200	[thread overview]
Message-ID: <v9psqcezf6.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: mailman.10871.1129036362.20277.help-gnu-emacs@gnu.org

On Tue, Oct 11 2005, Radomir Hejl wrote:

> On the second line of my file I have the following text:
> # -*- coding: utf-8;-*-
> The first line is an interpreter command.
[...]
> What should I fix to remedy this?

,----[ (info "(emacs)File Variables") ]
|    In shell scripts, the first line is used to identify the script
| interpreter, so you cannot put any local variables there.  To
| accommodate for this, when Emacs visits a shell script, it looks for
| local variable specifications in the _second_ line.
| 
|    A "local variables list" goes near the end of the file, in the last
| page.  (It is often best to put it on a page by itself.)  The local
| variables list starts with a line containing the string `Local
| Variables:', and ends with a line containing the string `End:'.  In
| between come the variable names and values, one set per line, as
| `VARIABLE: VALUE'.  The VALUEs are not evaluated; they are used
| literally.  If a file has both a local variables list and a `-*-' line,
| Emacs processes _everything_ in the `-*-' line first, and _everything_
| in the local variables list afterward.
| 
|    Here is an example of a local variables list: [...]
`----

Example:

# Local Variables: 
# coding: utf-8
# End: 

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

       reply	other threads:[~2005-10-11 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.10871.1129036362.20277.help-gnu-emacs@gnu.org>
2005-10-11 17:28 ` Reiner Steib [this message]
2005-10-11 19:49   ` specifying coding system on the first/second line Radomir Hejl
2005-10-12 15:44 ` Stefan Monnier
2005-10-12 19:49   ` Radomir Hejl
2005-10-11 12:55 Radomir Hejl

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=v9psqcezf6.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+from-uce@imap.cc \
    --cc=Reiner.Steib@gmx.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).