unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Ross Vandegrift <ross@kallisti.us>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to inspect hook variables with byte compilation
Date: Thu, 28 Sep 2023 10:02:21 +0200	[thread overview]
Message-ID: <87wmwa67zm.fsf@gmail.com> (raw)
In-Reply-To: <20230927173328.3jgldv4cezo22p4d@vanvanmojo.kallisti.us> (Ross Vandegrift's message of "Wed, 27 Sep 2023 10:33:28 -0700")

>>>>> On Wed, 27 Sep 2023 10:33:28 -0700, Ross Vandegrift <ross@kallisti.us> said:

    Ross> Hi folks,
    Ross> I'm using emacs 28.2 from Debian.  I'm trying to troubleshoot an issue
    Ross> with my org-mode setup.  So I inspect org-mode-hook with C-h v.

    Ross> The value is a byte-compiled function, and clicking on the bytecode
    Ross> gives me a disassemly.  How do I get human-readable output?

    Ross> Output:

    Ross>   org-mode-hook is a variable defined in ‘org.el’.

    Ross>   Its value is shown below.

    Ross>   Mode hook for Org mode, run after the mode was turned on.

    Ross>     This variable may be risky if used as a file-local variable.
    Ross>     You can customize this variable.

    Ross>   Value:
    Ross>   (#f(compiled-function
    Ross>       ()
    Ross>       #<bytecode -0x1356c8e47eb756a0>)
    Ross>      #f(compiled-function
    Ross>         ()
    Ross>         #<bytecode -0x1356c8e6dc1bfaa0>)
    Ross>      org-babel-result-hide-spec org-babel-hide-all-hashes)
    Ross>   Original value was nil

Find out which file is setting the org-mode-hook, and temporarily move
its .elc version out of the way.

Robert
-- 



  reply	other threads:[~2023-09-28  8:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 17:33 How to inspect hook variables with byte compilation Ross Vandegrift
2023-09-28  8:02 ` Robert Pluim [this message]
2023-09-28 15:43   ` Ross Vandegrift
2023-10-04 14:25     ` Robert Pluim

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=87wmwa67zm.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=ross@kallisti.us \
    /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).