Re: Bug located in `process-connection-type' (even in 21.1.14) (WAS: Re: [Adrian Aichner <adrian@xemacs.org>] Re: PCL-CVS shows Parser Errors in *cvs* buffer)

Jarl> Adrian.Aichner(a)t-online.de (Adrian Aichner) writes: >> >> Jarl> Adrian.Aichner(a)t-online.de (Adrian Aichner) writes: >> >> >> >> Jarl> I have made a very small program that demonstrates the Jarl> location of the bug. Essentially it is setting the variable Jarl> `process-connection-type' to nil that causes trouble. In the Jarl> Thank *you* for helping and commenting and taking the thread Jarl> seriously. Jarl> Modified version of what? pcl-cvs? XEmacs C code? net-utils? Jarl> I see, now I get it. to make it even easier I suggest the following Jarl> bug-reproducing code: Jarl> ,---- Jarl> | (let ( Jarl> | (mypassword "PaSsWoRd");;insert a password here Jarl> | (default-directory (cvs-expand-dir-name "~/projects/cvs-sandbox/xemacs-devel/packages")) Jarl> | ) Jarl> | (progn Jarl> | (setq process-connection-type nil) ; Use a pipe. Jarl> | (kill-buffer (get-buffer-create " *mycvs-tmp-pipe*")) Jarl> | (apply 'start-process "mycvs-pipe" (get-buffer-create " *mycvs-tmp-pipe*") "cvs" '("-f" "status")) Jarl> | (setq process-connection-type t) ; Use a pty. Jarl> | (kill-buffer (get-buffer-create " *mycvs-tmp-pty*")) Jarl> | (apply 'start-process "mycvs-pty" (get-buffer-create " *mycvs-tmp-pty*") "cvs" '("-f" "status")) Jarl> | (process-send-string "mycvs-pty" (concat mypassword "\n")) Jarl> | ) Jarl> | ) Jarl> `---- Jarl> To Steve (and other (unix) tester ): If there are "major" differences Jarl> in the two buffers, then that demonstrates the bug. Jarl> I'm not sure I understand what you mean here; "diffs" of Jarl> what? "do the same" as what? Jarl> I see. You should know I am not hooked up by that fast a line Jarl> (256kb/s) so doing a cvs status on the 'packages' module takes some Jarl> time. Jarl> Another thing is that it seem not very reproducible to me on Jarl> that module, but Steve had experienced this, Steve would you Jarl> please do the bug-demonstration on the 'packages' module? Jarl> Nevertheless getting this close I probably will continue Jarl> until fixed :-) I am competent in unix system C programmer Jarl> so I guess it's just a question of getting a grip of the Jarl> XEmacs C code. I may ask the guy who splitted Jarl> `process-unix.c' Kirill M. Katsnelson <kkm(a)kis.ru&gt;. Jarl> OK, cool. I am not sure of what it is, I see a lot of Jarl> comments and code snippets (in different colours) in the Jarl> file with names (probably authors). Is it such that I can Jarl> for any line in the code see who 'touch'ed this line last Jarl> time and when that happend? kind of who to blaim/contact for Jarl> the specific part of the code? Exactly, it's also referred to as the blame feature :-) It tells you who to ask about pieces of code. Of course this breaks down if the committer is not the author of the code. But the committer should be able to establish contact with the author. Jarl> Have a good holyday, it's my turn next friday; heading for Jarl> Val. T. on my snowboard :-DD) Jarl> I will continue for some time. Please catch me up on this I Jarl> tend to forget it, that is I'll be back from snow-land the Jarl> 10. February. Jarl> Were I surf there aren't any skiers anyway, they tend to Jarl> stick to the slopes, not the powder and cliff edges where I Jarl> hang out :-) I may be around the corner, beware! Jarl> Jarl -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/