Re: SIGPIPE not properly reset with 'trap - PIPE'

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > I noticed the following bash bug when using gnulib-tool. The script > below outputs > > foo: line 20: echo: write error: Broken pipe > foo: line 21: echo: write error: Broken pipe > > with bash 3.2.48(5)-release on GNU/Linux, whereas I think it should

command not found on remote server

Hello all, Some script on the remote server are called in .bash_profile, so they are accessible for the user. But when i send a command via ssh, and that my command call those script, it says command unknown... What can i do for it to work ? Thank you. -- View this message in context: http://w

Re: command not found on remote server

Dolphin06 wrote: > Hello all, > > Some script on the remote server are called in .bash_profile, so they are > accessible for the user. But when i send a command via ssh, and that my > command call those script, it says command unknown... > What can i do for it to work ? Either change your comman

Re: command not found on remote server

Can i do something like this : ssh [EMAIL PROTECTED] export PATH=$PATH:/other path/ ; script param right ? Chet Ramey wrote: > > Dolphin06 wrote: >> Hello all, >> >> Some script on the remote server are called in .bash_profile, so they are >> accessible for the user. But when i send a co

binding key sequence "js" to vi-command-mode?

I find Escape hard to get to in vi so I map the sequence "js" to it. I'm wondering if its possible to emulate this behavior in bash. I tried: bind -m vi-insert "js": vi-command-mode but it doesn't seem to work: typing the sequence from insert mode just beeps when j is typed and then the s

Re: command not found on remote server

Dolphin06 <[EMAIL PROTECTED]> wrote: > Can i do something like this : > ssh [EMAIL PROTECTED] export PATH=$PATH:/other path/ ; script param You'd have to quote the sequence of commands that should run on the remote host, so that the local bash and ssh see it as all one parameter: ssh [EMAIL PR

Re: SIGPIPE not properly reset with 'trap - PIPE'

Hello Andreas, * Andreas Schwab wrote on Thu, Dec 11, 2008 at 10:13:18AM CET: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > foo: line 20: echo: write error: Broken pipe > > foo: line 21: echo: write error: Broken pipe > > Please also note that the above errors occur also when > > trap ''

Re: SIGPIPE not properly reset with 'trap - PIPE'

Ralf Wildenhues writes: > That may well be, but if SIGPIPE is ignored upon script startup, then > the shell should not output those error messages upon receiving the > signal in the first place, no? When SIGPIPE is ignored then the syscall returns with EPIPE instead. This is what bash is reporti

Re: command not found on remote server

Paul Jarc wrote: > Dolphin06 wrote: > > Can i do something like this : > > ssh $u...@$server export PATH=$PATH:/other path/ ; script param > > You'd have to quote the sequence of commands that should run on the > remote host, so that the local bash and ssh see it as all one parameter: > ssh $u

Re: command not found on remote server

Bob Proulx wrote: > Also, using full paths is frowned upon. You mean invoking /directory/some-command directly instead of PATH=$PATH:/directory some-command ? It depends on the situation. If you think some-command is in /directory, but you want to allow for the possibility that it might be some

Re: SIGPIPE not properly reset with 'trap - PIPE'

Hi Ralf! Andreas Schwab wrote: > Ralf Wildenhues writes: > > I noticed the following bash bug when using gnulib-tool. The script > > below outputs > > > > foo: line 20: echo: write error: Broken pipe > > foo: line 21: echo: write error: Broken pipe > >... > > Please also note that the above error

Re: command not found on remote server

Paul Jarc wrote: > Bob Proulx wrote: > > Also, using full paths is frowned upon. > > You mean invoking /directory/some-command directly instead of > PATH=$PATH:/directory > some-command > ? Yes. That is what I am saying. > It depends on the situation. I can't disagree with that. > If you thin

Re: command not found on remote server

On Thu, Dec 11, 2008 at 03:35:33PM -0700, Bob Proulx wrote: > Paul Jarc wrote: > > Bob Proulx wrote: > > > Also, using full paths is frowned upon. > > > > You mean invoking /directory/some-command directly instead of > > PATH=$PATH:/directory > > some-command > > ? > ... > ... I was actually comme

Re: Readline redisplay bug with long prompt

Andreas Schwab wrote: > Bash Version: 3.2 > Patch Level: 48 > Release Status: release > > Description: > Redisplay fails if the prompt wraps around and contains invisible > characters after the wrap point. > > Repeat-By: > (assuming 80 column display) > $ > PS1='

Re: passing array to command line argument.

Dolphin06 wrote: > I dont get it right, i always display only the first one, and i dont know how > to write a scalar variable. > I tried like this : > ssh $u...@$server script2 -f "${my_arr...@]}" Stick an `echo' in front of this command and see what you're executing. -- ``The lyf so short, the