unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Patch to cus-edit.el
Date: Sun, 24 Feb 2002 10:20:03 +0100	[thread overview]
Message-ID: <rj1yfb2q4c.fsf@ssv2.dina.kvl.dk> (raw)

I added custom-unlispify-remove-prefixes to the custom-buffer
customize group, because I looked for it in that group and couldn't
find it.

In general, is it necessary to ask for permission to commit small
improvement to the customize specifications like this?  That is,
adding :group and :link entries to defcustoms, or improving :type
entries?

Is there even any reason to mention I do it here?

I will add ChangeLog entries, of course.

2002-02-24  Per Abrahamsen  <abraham@dina.kvl.dk>

	* cus-edit.el (custom-unlispify-remove-prefixes): Add to
	`custom-buffer' customize group.

*** cus-edit.el.~1.144.~	Mon Feb 11 16:10:33 2002
--- cus-edit.el	Sun Feb 24 09:30:47 2002
***************
*** 431,436 ****
--- 431,437 ----
  (defcustom custom-unlispify-remove-prefixes nil
    "Non-nil means remove group prefixes from option names in buffer."
    :group 'custom-menu
+   :group 'custom-buffer
    :type 'boolean)
  
  (defun custom-unlispify-menu-entry (symbol &optional no-suffix)

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


             reply	other threads:[~2002-02-24  9:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-24  9:20 Per Abrahamsen [this message]
2002-02-25  0:09 ` Patch to cus-edit.el Richard Stallman

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=rj1yfb2q4c.fsf@ssv2.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).