Juanma Barranquero wrote:
On 5/16/07, Lennart Borgman (gmail) <[EMAIL PROTECTED]> 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?
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
