> No, the original code is OK here. This is the body of > tla-show-changes-buffer, the process sentinel. If > tla-switch-to-buffer-first is true, the "switch-to-buffer" must have > been done before launching the process. > > This works well for M-x tla-changes RET, maybe this broke some other > commands, but that's not the place to fix it.
Thank you. It seems that the problem I met is nothing to do with `tla-switch-to-buffer-first'. See below. > Be carefull: an non-zero exit status is not allways an error. For > example, "tla changes" will exit with a status 1 if there are some > changes in the local tree. > > For tla star-merge, I'm not sure (it's not documented. See the > source :-( ). I think a status of 1 means there were some conflicts. > If this is the case, we need to test the value of "status" in > the :error handler, but not remove it. As far as my testing, at least the status is 2, it stands for an error. I introduce the default error handler is the status is 2. Thank you again.
