From: Jason Rumney <jasonrumney@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: programming file-extensions in .emacs
Date: Wed, 27 Feb 2008 08:20:34 -0800 (PST) [thread overview]
Message-ID: <6772c1fe-5321-41d6-9bba-74443a83b203@n58g2000hsf.googlegroups.com> (raw)
In-Reply-To: 6d54fc34-7e67-4dd0-9c99-be7796283cdb@e25g2000prg.googlegroups.com
On 27 Feb, 14:17, efrem <oleg-zhu...@hotmail.ru> wrote:
> I'd like to change the .emacs file in order to
> make some key-setting for the cases of xxxx.f and xxxx.cc files.
...
> What is the way to change this code it runs properly without any
> typings like "M-x mykeys": the .emacs must do these settings itself?
(add-hook 'fortran-mode-hook 'mykeys)
(add-hook 'c++-mode-hook 'mykeys)
The latter could be replaced with c-mode-common-hook if you want to
extend this to all C like programming languages.
next prev parent reply other threads:[~2008-02-27 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 14:17 programming file-extensions in .emacs efrem
2008-02-27 16:20 ` Jason Rumney [this message]
2008-02-27 16:25 ` Peter Dyballa
2008-02-27 16:55 ` Harald Hanche-Olsen
2008-02-28 7:36 ` efrem
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=6772c1fe-5321-41d6-9bba-74443a83b203@n58g2000hsf.googlegroups.com \
--to=jasonrumney@gmail.com \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).