From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Scott Lipcon" <slipcon@ugrad.cs.jhu.edu>, <zsh-users@sunsite.auc.dk>
Subject: RE: remote function problems.
Date: Wed, 12 Jan 2000 10:29:28 +0300 [thread overview]
Message-ID: <000201bf5cce$c2a9f5c0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <Pine.GSO.3.96.1000110234329.25844A-100000@hops.cs.jhu.edu>
You most probably have call to stty in your .zshrc or /etc/zshrc (that is being
executed for every interactive shell; and you force your shell to be interactive
with -i option).
1. Do not use -i option. Why do you need it?
2. Wrap call to stty around
if [[ -t 0 ]]; then
stty ...
fi
/andrej
> -----Original Message-----
> From: Scott Lipcon [mailto:slipcon@ugrad.cs.jhu.edu]
> Sent: Tuesday, January 11, 2000 7:49 AM
> To: zsh-users@sunsite.auc.dk
> Subject: remote function problems.
>
>
> Hello,
>
> I'm trying to write some function to distribute my config files among all
> the machines I use. For various reasons, I dont want to use rsync or CVS.
> I want to "push" the files out from my main machine, so I have a function
> which tars them up and scp's them to the remote machine (prompting for a
> password if necessary)
>
> I also have a function which installs the config files properly, from a
> tar file in my home directory. The problem is now executing that function
> remotely, via ssh.
>
> The best I've come up with is:
>
> $ ssh remote-host zsh -i -c function
>
> which runs the function, but also outputs:
>
> stty: standard input: Invalid argument
>
> is there a way to do this better?
>
> Thanks,
>
> Scott
>
>
next prev parent reply other threads:[~2000-01-12 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-11 4:49 Scott Lipcon
2000-01-12 7:29 ` Andrej Borsenkow [this message]
2000-01-12 18:52 ` Scott Lipcon
2000-01-12 19:20 ` Peter Stephenson
2000-01-13 8:43 ` Andrej Borsenkow
2000-01-13 9:32 ` Zefram
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='000201bf5cce$c2a9f5c0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=slipcon@ugrad.cs.jhu.edu \
--cc=zsh-users@sunsite.auc.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).