[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
How do I debug errors in post-command-hook?
From: |
Tassilo Horn |
Subject: |
How do I debug errors in post-command-hook? |
Date: |
Thu, 29 Jul 2010 22:30:58 +0200 |
User-agent: |
KMail/1.13.5 (Linux/2.6.35-rc6-git4; KDE/4.4.5; x86_64; ; ) |
Hi all,
how do I debug errors that happen while executing a function in
`post-command-hook'? The usual debugging facilities like
`toggle-debug-on-error' and `edebug-function' are not triggered in
there...
Background: There seem to be some packages that error when emacs is
started with the --daemon option. One example is the lusty-explorer's
`lusty-buffer-explorer' function. It works fine when run in a "normal"
emacs, but I get an error in `post-command-hook' when emacs was
initially started as daemon, and I'd like to know what's going wrong.
Bye,
Tassilo
- How do I debug errors in post-command-hook?,
Tassilo Horn <=
- Re: How do I debug errors in post-command-hook?, Lennart Borgman, 2010/07/29
- Re: How do I debug errors in post-command-hook?, Johan Bockgård, 2010/07/29
- Re: How do I debug errors in post-command-hook?, Tassilo Horn, 2010/07/30
- Re: How do I debug errors in post-command-hook?, Johan Bockgård, 2010/07/30
- Buffer names are sometimes read-only objects in daemonized emacs (was: How do I debug errors in post-command-hook?), Tassilo Horn, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Johan Bockgård, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Tassilo Horn, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Wojciech Meyer, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Tassilo Horn, 2010/07/30
- Re: Buffer names are sometimes read-only objects in daemonized emacs, Wojciech Meyer, 2010/07/30