From: Tim Johnson <tim@johnsons-web.com>
Subject: Re: Restricting 'add-hook to a specific file extension
Date: Mon, 06 Mar 2006 02:59:10 -0000 [thread overview]
Message-ID: <slrne0n7s4.pfc.tim@linus.johnson.com> (raw)
In-Reply-To: 87k6b8o9sg.fsf-monnier+gnu.emacs.help@gnu.org
On 2006-03-05, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> 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, I'm going to make you an offer, but first FYI:
I code for a living, I've got 6 kids, 10 brother and sisters, aged
parents and I belong to 2 churches. My R&D time is *very* limited.
Your name is all over the place when I google keywords related to this
topic, and I'm sure that you are an authority on this topic.
So here's the offer: I'd *like* to create a derived-mode for the
newlisp language, which is a lisp variant. I want it to be
cross-compatible to Xemacs (which doesn't support
font-lock-add-keywords).
Give me a hand (via this newsgroup) and I will give you full credit for
the results.
I don't care about the credit. I just want to make it work.
If you agree, and should you also think that this subject should expand
to a tutorial, howto or wike component I will do the grunt work,
documentation, whatever.
I moved from vim to emacs a little over a year ago, I have found
customizing for programming modes far more difficult than in vim and
from my research in newsgroups and googling, I believe that I'm not the
only one.
We could contribute significantly to the literature, methinks.
Thanks
tim
--
Tim Johnson <tim@johnsons-web.com>
http://www.alaska-internet-solutions.com
next prev parent reply other threads:[~2006-03-06 2:59 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
2006-03-06 2:59 ` Tim Johnson [this message]
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=slrne0n7s4.pfc.tim@linus.johnson.com \
--to=tim@johnsons-web.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.
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).