|
From: | Lennart Borgman (gmail) |
Subject: | Re: Debug on error and Emacs client |
Date: | Wed, 16 May 2007 15:06:24 +0200 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666 |
Juanma Barranquero wrote:
On 5/16/07, Lennart Borgman (gmail) <address@hidden> wrote:- It is not necessarily "emacsclient -e BIG-COMMAND-LINE-MISTAKE", it could equally well be somewhere in the elisp libraries.Fair enough, though if you set debug-on-error to debug the problem, it will happen also if you evaluate the code from inside Emacs (as opposed to "from emacsclient").
Some errors are very hard to track down. I think it can help very much to be able to directly debug what happens when the call is from emacsclient.
- If you use "-n" you will see nothing as it is now.That's no reason, I think. If you're worried about errors, don't use -n.
It might not be the right thing to do in all cases.BTW, does emacsclient exit with an error when there is an error evaluating the code that is sent from emacsclient?
[Prev in Thread] | Current Thread | [Next in Thread] |