From: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>
To: emacs-devel@gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Nic Ferrier <nferrier@ferrier.me.uk>
Subject: Re: why do some programming modes have customize hooks and others do not?
Date: Mon, 20 Oct 2014 00:44:18 +0200 [thread overview]
Message-ID: <2128728.y75FreRA9t@descartes> (raw)
In-Reply-To: <jwvvbnhf425.fsf-monnier+emacs@gnu.org>
On Saturday 18 October 2014 17:46:14 Stefan Monnier wrote:
> Maybe define-derived-mode should define the hook with defcustom.
> I guess we'd need some motivation (other than "consistency") for that,
> such as what would be the benefit to define the hook as a defcustom if
> all the defcustom says is ":type hook".
I've started working on a patch to add `:options' flags to mode hooks, such as
`imenu-add-menubar-index' for modes supporting imenu or `eldoc-mode' for modes
supporting eldoc. In that process I started adding `defcustom' for hooks to
modes which lacked one. Since I'm currently busy with real work I stopped
working on it. If there is interest I could push the current state. But this
could of course also be a motivation to add such a feature to `define-derived-
mode'. Although I'm not sure how to best represent it. A `:hook-options'
would probably miss the point. Maybe a `:supported-minor-modes' option?
Regards,
Rüdiger
next prev parent reply other threads:[~2014-10-19 22:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 11:10 why do some programming modes have customize hooks and others do not? Nic Ferrier
2014-10-18 11:37 ` Bastien
2014-10-18 21:46 ` Stefan Monnier
2014-10-18 22:24 ` Nic Ferrier
2014-10-19 22:44 ` Rüdiger Sonderfeld [this message]
2014-10-20 2:15 ` Stefan Monnier
2014-10-20 8:17 ` Nic Ferrier
2014-10-20 10:38 ` Artur Malabarba
2014-10-20 10:54 ` Nic Ferrier
2014-10-20 12:07 ` Artur Malabarba
2014-10-20 16:47 ` Stefan Monnier
2014-10-20 18:29 ` Nic Ferrier
2014-10-20 16:02 ` Stefan Monnier
2014-10-20 19:11 ` Nic Ferrier
2014-10-20 20:39 ` Stefan Monnier
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=2128728.y75FreRA9t@descartes \
--to=ruediger@c-plusplus.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nferrier@ferrier.me.uk \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).