From: luke.olbrish@cc.gatech.edu (Luke A. Olbrish)
Subject: Re: different modes for file with same extension?
Date: 21 Sep 2002 17:06:20 -0400 [thread overview]
Message-ID: <7vd6r7giib.fsf@gehennom.net> (raw)
In-Reply-To: amilvs$k3t$2@oden.abc.se
stig <nospam_stigerikson@yahoo.se> writes:
> is it possible to set up emacs to understand that two files with the same
> extension are actually written in two different programming languages?
>
> perl = .pl
> prolog = .pl
>
> same extensions, but very different code.
>
> would it be possible, and in that case how?
Make your first line in the file like this:
<comment specific to that mode> -*- mode: <mode-name> -*-
for example:
;; -*- mode: emacs-lisp -*-
or
// -*- mode: java -*-
--
Luke Olbrish
<luke.olbrish@cc.gatech.edu>
prev parent reply other threads:[~2002-09-21 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 20:48 different modes for file with same extension? stig
2002-09-21 21:06 ` Luke A. Olbrish [this message]
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=7vd6r7giib.fsf@gehennom.net \
--to=luke.olbrish@cc.gatech.edu \
/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).