all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Nic Ferrier <nferrier@ferrier.me.uk>
Cc: =?windows-1252?Q?R=FCdiger?= Sonderfeld <ruediger@c-plusplus.de>,
	emacs-devel@gnu.org
Subject: Re: why do some programming modes have customize hooks and others do not?
Date: Mon, 20 Oct 2014 12:02:35 -0400	[thread overview]
Message-ID: <jwvd29mag3z.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <871tq36tpl.fsf@ferrier.me.uk> (Nic Ferrier's message of "Mon, 20 Oct 2014 09:17:26 +0100")

> If I sent patches (once we're on git, how goes that?)

Same as for Bzr, yes.

> for customize any hooks that aren't already customizable, they would
> get accepted?

Depends on the specifics.  E.g. just changing the defcustom with a ":type
'hook" would probably not be accepted because the downside (pointed out
by Artur) isn't made up by significant extra convenience.
But if the change includes some genuinely useful extra info (e.g. good
suggestions for functions to add to this particular hook), it might make
it acceptable.


        Stefan



  parent reply	other threads:[~2014-10-20 16:02 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=jwvd29mag3z.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=nferrier@ferrier.me.uk \
    --cc=ruediger@c-plusplus.de \
    /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.