[EMAIL PROTECTED] (Edgar Gonçalves) writes: >> Stephen Leake <[EMAIL PROTECTED]> writes: >> >>> The core problem is that dvc-run-dvc-async wants to capture stderr as >>> well as stdout from the child processes. Emacs 'start-process' does >>> not allow that, and in fact does not say what happens to stderr. >>> Perhaps we could request that Emacs add a variant of start-process >>> that captures stderr in a separate buffer, but that won't happen for a >>> long time, if at all.
It turns out that start-process arranges for both stderr and stdout to go to the buffer; I tested it. I'll suggest on the emacs-devel list that the manual be updated. >>> So dvc-run-dvc-async explicitly spawns "sh", rather than the backend >>> executable. So this is actually unnecessary. I'll try changing it. That may have other consequences; we'll see. >> Stephen, thanks for the comprehensive analysis! You're welcome. > Hi! I'm still using DVC, but I stopped following its development for > a while. I've just retrieved the latest dev version, removed my > patch, as you sugested and yes, I confirm that bzr.exe now runs > without problems. I remember my patch to be needed in bzr's very > early stages! My only configuration is now the following: > > (require 'dvc-autoloads) > (setq bzr-executable "bzr") > > > And all the magic is done properly. So yes, you should have the patch in > question removed! Ok. I'll work on pushing my bzr repository to my website, rather than post the patch here. -- -- Stephe _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
