unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: ishikawa <chiaki.ishikawa@ubin.jp>
To: martin rudalics <rudalics@gmx.at>
Cc: ishikawa <chiaki.ishikawa@ubin.jp>, bug-gnu-emacs@gnu.org
Subject: Re: Strange error caused by post-command-hook.
Date: Thu, 12 Jul 2007 17:00:56 +0900	[thread overview]
Message-ID: <4695DFB8.5060202@ubin.jp> (raw)
In-Reply-To: <4695404B.8070706@gmx.at>

Dear Martin Rudalics,

Thank you for the additional information.

I am now trying to figure out where minibuffer-setup-hook is set.
Things get quite interesting. It seems that there are certainly more
references to minibuffer-setup-hook than to post-command-hook, etc..

I need to refresh my knowledge of edebug now.

Thank you again.

Chiaki Ishikawa

martin rudalics wrote:
>  > I tried the following mods to record what is inside post-command-hook.
>  > But this is too verbose and I wonder if there is a way to
>  > record the output of Fmessage() only to *Message* file
>  > instead of showing it to the minibuffer.
> 
> My previous suggestions were rather silly.  The bug should occur with
> `minibuffer-setup-hook', that is, within `minibuffer-with-setup-hook'.
> You'd have to identify an object in your .emacs that causes
> `minibuffer-setup-hook' to add a function to `post-command-hook' that's
> triggering the bug, likely somewhere within `find-file-read-args'.
> Could you try to edebug the latter?
> 
> 

  reply	other threads:[~2007-07-12  8:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 12:35 Strange error caused by post-command-hook ishikawa
2007-07-10 13:52 ` martin rudalics
2007-07-11  9:30   ` ishikawa
2007-07-11 11:47     ` martin rudalics
2007-07-11 12:10       ` ishikawa
2007-07-11 12:27         ` ishikawa
2007-07-11 20:40           ` martin rudalics
2007-07-12  8:00             ` ishikawa [this message]
2007-07-12  8:54               ` martin rudalics
2007-07-11 14:24         ` martin rudalics
2007-07-11 11:53     ` ishikawa

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=4695DFB8.5060202@ubin.jp \
    --to=chiaki.ishikawa@ubin.jp \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=rudalics@gmx.at \
    /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).