|
From: Sashi on 2 Nov 2006 16:10 I ran 'set -n' at the prompt and now it refuses to execute my commands! Solaris 5.8. Er, how do I get out? I put a couple of jobs in the background and would prefer to bring ths terminal back to life rather than simply kill it. Thanks, Sashi
From: Jordan Abel on 2 Nov 2006 16:32 2006-11-02 <1162501821.623003.23190(a)m7g2000cwm.googlegroups.com>, Sashi wrote: > I ran 'set -n' at the prompt and now it refuses to execute my commands! > > Solaris 5.8. > > Er, how do I get out? I put a couple of jobs in the background and > would prefer to bring ths terminal back to life rather than simply kill > it. send an eof. or several. what shell are you using? set -n is ignored on bash and (this may vary) ksh, and rejected on zsh.
From: Stephane CHAZELAS on 2 Nov 2006 16:39 2006-11-2, 21:32(+00), Jordan Abel: > 2006-11-02 <1162501821.623003.23190(a)m7g2000cwm.googlegroups.com>, > Sashi wrote: >> I ran 'set -n' at the prompt and now it refuses to execute my commands! >> >> Solaris 5.8. >> >> Er, how do I get out? I put a couple of jobs in the background and >> would prefer to bring ths terminal back to life rather than simply kill >> it. > > send an eof. or several. That will terminate the shell though. There may not be any better solution to that problem, though. > what shell are you using? set -n is ignored on bash and (this may vary) ksh, and > rejected on zsh. I beleive he is using the Bourne shell. SUSv3 says that an interactive shell may ignore a "set -n" so a POSIX shell may also behave like that though as you point out, except for ash based shells, there doesn't seem to be any that does (someone must have run into the problem and decided to fix it). -- St?phane
From: Sashi on 2 Nov 2006 16:55 Stephane CHAZELAS wrote: > 2006-11-2, 21:32(+00), Jordan Abel: > > 2006-11-02 <1162501821.623003.23190(a)m7g2000cwm.googlegroups.com>, > > Sashi wrote: > >> I ran 'set -n' at the prompt and now it refuses to execute my commands! > >> > >> Solaris 5.8. > >> > >> Er, how do I get out? I put a couple of jobs in the background and > >> would prefer to bring ths terminal back to life rather than simply kill > >> it. > > > > send an eof. or several. > > That will terminate the shell though. There may not be any > better solution to that problem, though. > > > what shell are you using? set -n is ignored on bash and (this may vary) ksh, and > > rejected on zsh. > > I beleive he is using the Bourne shell. > > SUSv3 says that an interactive shell may ignore a "set -n" so a > POSIX shell may also behave like that though as you point out, > except for ash based shells, there doesn't seem to be any that > does (someone must have run into the problem and decided to fix > it). > > -- > Stéphane Sorry, here you go. $bash -version GNU bash, version 2.03.0(1)-release (sparc-sun-solaris) Copyright 1998 Free Software Foundation, Inc. The man page for set specifically says that the -n option is ignored for interactive shells (and it's easy to see why). Thanks, Sashi
From: Jordan Abel on 2 Nov 2006 18:21 2006-11-02 <1162504522.926549.113360(a)k70g2000cwa.googlegroups.com>, Sashi wrote: > > Stephane CHAZELAS wrote: >> 2006-11-2, 21:32(+00), Jordan Abel: >> > 2006-11-02 <1162501821.623003.23190(a)m7g2000cwm.googlegroups.com>, >> > Sashi wrote: >> >> I ran 'set -n' at the prompt and now it refuses to execute my commands! >> >> >> >> Solaris 5.8. >> >> >> >> Er, how do I get out? I put a couple of jobs in the background and >> >> would prefer to bring ths terminal back to life rather than simply kill >> >> it. >> > >> > send an eof. or several. >> >> That will terminate the shell though. There may not be any >> better solution to that problem, though. >> >> > what shell are you using? set -n is ignored on bash and (this may vary) ksh, and >> > rejected on zsh. >> >> I beleive he is using the Bourne shell. >> >> SUSv3 says that an interactive shell may ignore a "set -n" so a >> POSIX shell may also behave like that though as you point out, >> except for ash based shells, there doesn't seem to be any that >> does (someone must have run into the problem and decided to fix >> it). >> >> -- >> St?phane > > > Sorry, here you go. > > $bash -version > GNU bash, version 2.03.0(1)-release (sparc-sun-solaris) > Copyright 1998 Free Software Foundation, Inc. > > The man page for set specifically says that the -n option is ignored > for interactive shells (and it's easy to see why). So evidently that's not what you're using, or it would have been ignored and you'd never have posted this thread.
|
Next
|
Last
Pages: 1 2 3 Prev: sed: illegal option -- r when running bibexport.sh Next: Finding end of file |