[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ad-interactive-form vs interactive-form
From: |
raman |
Subject: |
Re: ad-interactive-form vs interactive-form |
Date: |
Fri, 27 Jul 2007 07:34:22 -0700 (PDT) |
Hi Stefan,
This is a follow-up to the message I sent
earlier this morning.
I spotted the cause of the problem that I was hitting when using
interactive-form instead of ad-interactive-form:
interactive-form returns the autoload list for autoloaded functions,
ad-interactive-form used to return nil.
I therefore needed to add a check for (functionp (symbol-function sym))
before allowing Emacspeak to go off and auto-hack interactive functions.
Incidentaly, that corner of Emacspeak is a particularly hairy piece of
code that does:
0) Find functions that use an interactive spec for declaring their
prompts. 1) For those decls that dont use the minibuffer, perform
surgery to make those functions use the minibuffer.
The above was needed for a large number of functions until Emacs 21
--- since most prompting resulting from interactive decls happened
directly through the C code in callint.c -- and consequently, Emacspeak
making functions like read-from-minibuffer or read-file-name was not
sufficient --- I needed to do the work to perform run-time surgery to
functions that used interactive. As of emacs 21, I only need to do this
to commands that use either 'c' or 'k' in their interactive spec --
would be nice to make those prompts go through the lisp layer as well --
in which case I could get rid of emacspeak-fix-interactive entirely.
- Re: ad-interactive-form vs interactive-form,
raman <=