From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Restricting 'add-hook to a specific file extension
Date: Sun, 05 Mar 2006 16:38:20 -0500 [thread overview]
Message-ID: <87k6b8o9sg.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.5.1140910129.18076.help-gnu-emacs@gnu.org
> One solution is derived-mode, but I've had no luck with it.
Try harder. No matter how hard it looks, it'll be easier than trying to fix
the problems you'll get with the other approach.
Stefan
next prev parent reply other threads:[~2006-03-05 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1140910129.18076.help-gnu-emacs@gnu.org>
2006-02-26 4:28 ` Restricting 'add-hook to a specific file extension Barry Margolin
2006-02-26 23:49 ` Tim Johnson
2006-02-27 1:26 ` Barry Margolin
2006-03-01 19:04 ` Kevin Rodgers
[not found] ` <mailman.125.1141286170.2835.help-gnu-emacs@gnu.org>
2006-03-06 2:59 ` Tim Johnson
2006-03-01 23:42 ` Nate Thern
2006-03-05 21:38 ` Stefan Monnier [this message]
2006-03-06 2:59 ` Tim Johnson
2006-03-06 8:41 ` Stefan Monnier
2006-03-06 17:59 ` Tim Johnson
2006-02-25 23:40 Tim Johnson
2006-02-27 16:42 ` Kevin Rodgers
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=87k6b8o9sg.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
/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).