From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: ~`symbol-function' to get code as list even when byte-compiled?
Date: Mon, 25 May 2015 04:52:55 +0200 [thread overview]
Message-ID: <877frxid14.fsf@debian.uxu> (raw)
(re-search-forward "^Question")
Here is some interesting code. What's interesting is:
when this code executes, it changes itself, i.e.
the code changes the code!
But it isn't a macro which is a program that produces
a new program based on its own logic and non-evaluated
input data.
On the contrary, here we deal all with ordinary
functions (defuns) where one changes the other.
Does that always happen? No - only when it is needed!
See the entire code here [1]. Go there if you want to
see this in execution as it probably is based on some
other functions as well. The below code is for display
purposes ONLY!
Question: this is all working thanks to
`symbol-function' which is used to get the code of the
function as data, so it can be examined and
manipulated. However, if I byte-compile the code
(which I always do), `symbol-function' doesn't return
a lambda function which is also a list, but instead
just a function #[...] which isn't a list. So then it
doesn't work!
I was able to do a workaround with `load-file' in
.emacs to get all the functions in the file in
evaluated form. But, can I do that specifically for
a named function, *or*, can I extract the code in list
format somehow even if compiled?
(symbol-function jump)
(defun enable-jump (jump)
(add-hook 'w3m-display-hook jump)
(let*((code (symbol-function jump))
(remove-code `(remove-hook 'w3m-display-hook (quote ,jump)))
(remove-code-index 2)
(current-code (nth remove-code-index code)) )
(unless (equal current-code remove-code)
(push remove-code (nthcdr remove-code-index code)) )))
(defun web-search ()
(interactive)
(let ((search (get-search-string "Google")))
(unless (empty-string-p search)
(w3m-new-tab (format "Google: %s" search))
(w3m-search w3m-search-default-engine search) ))
(enable-jump 'number-one-jump) )
(defun number-one-jump (&optional not-used) ; Google, Youtube
(when (re-search-forward "^ 1." (point-max) t)
(recenter-top-bottom 0)
(w3m-next-anchor) ))
[1] http://user.it.uu.se/~embe8573/conf/emacs-init/w3m/w3m-unisearch.el
--
underground experts united
http://user.it.uu.se/~embe8573
next reply other threads:[~2015-05-25 2:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 2:52 Emanuel Berg [this message]
2015-05-25 2:58 ` ~`symbol-function' to get code as list even when byte-compiled? Barry Margolin
2015-05-25 17:16 ` Emanuel Berg
2015-05-25 17:37 ` Pascal J. Bourguignon
2015-05-25 3:10 ` Pascal J. Bourguignon
2015-05-25 17:07 ` Emanuel Berg
2015-05-25 17:18 ` Pascal J. Bourguignon
[not found] ` <mailman.3638.1432574334.904.help-gnu-emacs@gnu.org>
2015-05-25 17:41 ` Emanuel Berg
2015-05-25 17:48 ` Pascal J. Bourguignon
[not found] ` <mailman.3640.1432576116.904.help-gnu-emacs@gnu.org>
2015-05-26 0:01 ` Emanuel Berg
2015-05-26 0:12 ` Emanuel Berg
2015-05-26 20:34 ` Stefan Monnier
2015-05-26 23:02 ` Emanuel Berg
2015-05-27 1:07 ` Stefan Monnier
2015-05-27 1:31 ` Emanuel Berg
2015-05-27 1:55 ` Stefan Monnier
2015-05-27 2:20 ` Emanuel Berg
2015-05-27 2:31 ` Stefan Monnier
2015-05-27 23:49 ` Emanuel Berg
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=877frxid14.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.org \
/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.
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).