all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Creating new major mode
Date: Thu, 25 Sep 2008 15:36:58 +1000	[thread overview]
Message-ID: <87d4is6b2d.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.19863.1222293135.18990.help-gnu-emacs@gnu.org

"Paulo J. Matos" <pocm@ecs.soton.ac.uk> writes:

> On Wed, Sep 24, 2008 at 4:06 PM, Nikolaj Schumacher <me@nschum.de> wrote:
>> Paulo Jorge Matos <pocm@soton.ac.uk> wrote:
>>
>>> Thank you. It seems then that the issue is that some modes predate the
>>> existence of the derived-mode API. New modes should use though, right?
>>
>> Well, "should" is relative.  I absolutely suggest it, but it's strictly
>> optional.  Some newer modes also elect not to use it.
>>
>> Maybe take a look at the bundled css-mode.  It's not too big and has a
>> typical design.
>>
>
> Thanks for the tip, I will look at it! :)
>

The other nice thing about using derived mode et al is that you can get
a lot of functionality for free. For example, if you derive from a mode
that has the same basic formatting requirements as your new mode, then
you only need to tweak things rather than re-invent from scratch. 
It can be a lot less work and result in a lot less you need to maintain.

Tim


-- 
tcross (at) rapttech dot com dot au


      parent reply	other threads:[~2008-09-25  5:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23  9:28 Creating new major mode Paulo Jorge Matos
2008-09-23 18:58 ` Nikolaj Schumacher
     [not found] ` <EMEW-k8MK2cf73177e81b278b031d7d8b57c991f680-m263om664x.fsf@nschum.de>
2008-09-24  9:05   ` Paulo Jorge Matos
2008-09-24 15:06     ` Nikolaj Schumacher
2008-09-24 21:52       ` Paulo J. Matos
     [not found]       ` <mailman.19863.1222293135.18990.help-gnu-emacs@gnu.org>
2008-09-25  5:36         ` Tim X [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d4is6b2d.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.