unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Hourihan <jimh@tweakfilms.com>
Cc: emacs-devel@gnu.org
Subject: Re: pcl-cvs help
Date: Tue, 28 Jan 2003 11:28:58 -0800	[thread overview]
Message-ID: <m23cnd9ipx.fsf@corn.tweak.local> (raw)
In-Reply-To: <200301281726.h0SHQ4w04066@rum.cs.yale.edu> ("Stefan Monnier"'s message of "Tue, 28 Jan 2003 12:26:04 -0500")

"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:

>> David Caldwell <david@porkrind.org> writes:
>> 
>> > This seemed to eliminate the problem for me (from Andrew's FAQ):
>> > 
>> > (setq process-connection-type nil)
>> 
>> There is a problem with the implementation of ptys on the Mac OS X.
>> That was why I set process-connection-type to nil by default in
>> lisp/term/mac-win.el.  At some point, this was conditioned out without
>> my knowledge.  If no one can provide a good reason for doing this, I
>> propose to change it back the way it was.
>
> Hmmmm so if CVS' output is a pipe, PCL-CVS hits the CVS+SSH+libc+pipe problem
> and if it's a pty, it hits the other problem.
>
> IIRC, one way to get things working is to use a pipe (as it should,
> and as it was doing in Emacs-21.2) and to set CVS_RSH not to `ssh'
> but to a script like
>
> 	#!/bin/sh
> 	(ssh "$@" 2>&1 1>&3 | cat) 3>&1 1>&2
>
> that runs ssh's stderr through `cat'.  Jim, can you try that ?

It works! Both OS X and Linux are now working flawlessly (fingers
crossed). Thank god too because this has been driving me nuts! I reverted
the pcvs.el file to its shipped state by uncommenting out this line in
cvs-run-process:

          (process-connection-type nil) 

That fixed the problem. I tried cvs-status on our entire source tree and it
worked. If something goes wrong with it I'll know in the next couple of
days. 

          -Jim

  reply	other threads:[~2003-01-28 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m28yxbd69c.fsf@corn.tweak.local>
     [not found] ` <5l65sfa2t2.fsf@rum.cs.yale.edu>
     [not found]   ` <200301232349.h0NNnWo09694@rum.cs.yale.edu>
     [not found]     ` <200301240123.h0O1NK022670@champion.sslsecure.com>
2003-01-27 17:39       ` pcl-cvs help Stefan Monnier
2003-01-27 19:16         ` Jim Hourihan
2003-01-27 23:43           ` David Caldwell
2003-01-28  0:14             ` Andrew Choi
2003-01-28 17:26               ` Stefan Monnier
2003-01-28 19:28                 ` Jim Hourihan [this message]
2003-01-29  6:36             ` Richard Stallman
2003-01-29  7:05               ` Andrew Choi
2003-01-30 15:20                 ` Richard Stallman
2003-01-30 15:54                   ` Andrew Choi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m23cnd9ipx.fsf@corn.tweak.local \
    --to=jimh@tweakfilms.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).