On 5/16/07, Lennart Borgman (gmail) <[EMAIL PROTECTED]> wrote:
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.
Perhaps you're right, but I'd like to see some examples of things that
are much easier to debug from --eval than directly.
It might not be the right thing to do in all cases.
No. But if it is normal operation for your emacsclient invocation to
fail sometimes, it'd be sensible to *not* use -n and read
emacsclient's stderr output and exit code; and if it is not normal,
the moment you detect a problem you can remove the -n and try again.
This is not to say that I oppose the feature; I just don't feel it
compelling right now (but I can be easily convinced :)
BTW, does emacsclient exit with an error when there is an error
evaluating the code that is sent from emacsclient?
Not currently, no. It returns an error for any trouble communicating
with Emacs, not because of what happens to the info exchanged between
them.
Juanma
_______________________________________________
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
