Re: Why post-command-hook so difficult to debug?

[Tassilo Horn]

Leo <address@hidden> writes:

Hi Leo!

> For example, some days ago I was seeing this error:
>
> Error in post-command-hook (completion-in-region--postch): 
> (wrong-type-argument characterp 134217855)
>
> and it turned out the error was generated by another function 100 miles
> from completion-in-region--postch.  debug-on-error is mostly useless in
> this case.

I'm having a very similar error right now, 

  Error in post-command-hook (completion-in-region--postch):
    (wrong-type-argument stringp nil)

I've stared at the definition of `completion-in-region--postch', and
probably the error happens in the the form:

    (funcall completion-in-region-mode--predicate)

Of course, now I can't reproduce it anymore... :-(

Anyway, could you please elaborate what was the 100 miles away function
in your case?  Maybe it's similar here...

Bye,
Tassilo