unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Ryde <user42@zip.com.au>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 5327@debbugs.gnu.org
Subject: bug#5327: 23.1; unload-feature-special-hooks add  fill-nobreak-predicate
Date: Sat, 09 Jan 2010 08:28:10 +1100	[thread overview]
Message-ID: <87ocl4e179.fsf@blah.blah> (raw)
In-Reply-To: <f7ccd24b1001051730p5076115p2e6854bea0015aaf@mail.gmail.com> (Juanma Barranquero's message of "Wed, 6 Jan 2010 02:30:26 +0100")

Juanma Barranquero <lekktu@gmail.com> writes:
>
> The question is
> whether there are many variables called -functions which are not
> really hooks.

That'd be the dangerous bit.  I've got a defconst called -functions in
some of my code, but it wouldn't be hurt.

Those with a custom-type of 'hook or '(repeat function) could be likely.
In fact any var with that custom-type might be ok to act on.  A grep
finds me three called -functions (code below)

    find-directory-functions
    auto-coding-functions
    compile-command-default-functions

of which auto-coding-functions may be the only important one not
presently in unload-feature-special-hooks.




(pp (let (ret)
      (mapatoms (lambda (sym)
                  (and (boundp sym)
                       (get sym 'custom-type)
                       (not (memq sym unload-feature-special-hooks))
                       (string-match "-functions\\'" (symbol-name sym))
                       (push (list sym (get sym 'custom-type)) ret))))
      ret)
    (current-buffer))






  reply	other threads:[~2010-01-08 21:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 23:38 bug#5327: 23.1; unload-feature-special-hooks add fill-nobreak-predicate Kevin Ryde
2010-01-06  1:30 ` Juanma Barranquero
2010-01-08 21:28   ` Kevin Ryde [this message]
2011-07-11 16:25 ` Juanma Barranquero
2011-07-16  1:52   ` Kevin Ryde

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=87ocl4e179.fsf@blah.blah \
    --to=user42@zip.com.au \
    --cc=5327@debbugs.gnu.org \
    --cc=lekktu@gmail.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.
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).