zsh-users
 help / color / mirror / code / Atom feed
From: Meino Christian Cramer <Meino.Cramer@gmx.de>
To: arvidjaar@newmail.ru
Cc: zsh-users@sunsite.dk
Subject: Re: More general zsh-scripting question
Date: Sun, 22 May 2005 13:13:29 +0200 (CEST)	[thread overview]
Message-ID: <20050522.131329.93018533.Meino.Cramer@gmx.de> (raw)
In-Reply-To: <200505221303.05457.arvidjaar@newmail.ru>

From: Andrey Borzenkov <arvidjaar@newmail.ru>
Subject: Re: More general zsh-scripting question
Date: Sun, 22 May 2005 13:03:04 +0400

> On Sunday 22 May 2005 09:00, Meino Christian Cramer wrote:
> >  For example these two lines are part of a function defined inside a
> > script:
> >
> >  cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/snd login
> >  cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/snd update -d
> > cvs-snd index=1
> >
> 
> Why do you need cvs login in script? You only have to do login once, then CVS 
> remembers login/password/repository combination and does not ask for it 
> anymore.

  As I mentioned I have a couple of projects from the net for which I
  do updates via cvs. Not all use the same cvs server. cvs only stores
  one login/password/repository combination.
 
> >
> >  When the second line is executed, the login: prompt stops execution
> >  of the script and waits for the <RETURN>.
> >
> >  Is there a way to automate this ?
> >
> 
> if you still insist on it
> 
> expect
> zpty module that is part of zsh
> 
> zsh has some examples of using zpty to drive interactive programs, like 
> nslookup wrapper.
> 
> -andrey

I will try that, thanks!

Meino


  reply	other threads:[~2005-05-22 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-22  5:00 Meino Christian Cramer
2005-05-22  9:03 ` Andrey Borzenkov
2005-05-22 11:13   ` Meino Christian Cramer [this message]
2005-05-22 12:11 ` Hannu Koivisto

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

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

  git send-email \
    --in-reply-to=20050522.131329.93018533.Meino.Cramer@gmx.de \
    --to=meino.cramer@gmx.de \
    --cc=arvidjaar@newmail.ru \
    --cc=zsh-users@sunsite.dk \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).