all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Help debug an error in pre-command-hook?
Date: Thu, 09 Feb 2012 19:25:02 +0100	[thread overview]
Message-ID: <4F340F7E.3060200@gmx.at> (raw)
In-Reply-To: <m1wr7ws8xb.fsf@gmail.com>

 > Error in pre-command-hook:
 >
 > (wrong-type-argument symbolp (lambda (&rest --cl-rest--) (interactive)
 > (apply (lambda (G91516 G91517 G91518) (setq
 > minor-mode-overriding-map-alist (symbol-value G91518)) (bury-buffer) (if
 > (and (symbol-value G91517) (not (one-window-p))) (delete-window)) (if
 > (window-live-p (symbol-value G91516)) (select-window (symbol-value
 > G91516)))) (quote --origwin--) (quote --delete-p--) (quote --old--)
 > --cl-rest--)))
 >
 > Before the error, the value of pre-command-hook is:
 >
 >    pre-command-hook is a variable defined in `C source code'.
 >    Its value is (t comint-preinput-scroll-to-bottom)
 >
 >    Local in buffer *Python*; global value is
 >    (delete-selection-pre-hook tooltip-hide)
 >
 >
 > But looking at the source of comint-preinput-scroll-to-bottom, I cannot
 > see where it can generate this error? Any idea how to debug this?

I can neither find

(setq minor-mode-overriding-map-alist

nor

origwin

anywhere in the Emacs sources so maybe this is something from your
customizations or a package you load.  Try printing the values of
`pre-command-hook' from within `comint-preinput-scroll-to-bottom'.

martin



  reply	other threads:[~2012-02-09 18:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09  8:33 Help debug an error in pre-command-hook? Leo
2012-02-09 18:25 ` martin rudalics [this message]
2012-02-09 22:20 ` Stefan Monnier
2012-02-13  8:08   ` Leo

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F340F7E.3060200@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.