zsh-workers
 help / color / mirror / code / Atom feed
* 3.0-pre1 odd behavior
@ 1996-07-02 23:50 Clint Olsen
  1996-07-03  4:52 ` Bart Schaefer
  0 siblings, 1 reply; 7+ messages in thread
From: Clint Olsen @ 1996-07-02 23:50 UTC (permalink / raw)
  To: zsh-workers

Hello:

Is this a new feature?

misha ~# more \-
Usage: more [-dfln] [+linenum | +/pattern] name1 name2 ...
zsh: exit 1     more -

I've never seen zsh report exit status on jobs in the foreground before.

-Clint



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0-pre1 odd behavior
  1996-07-02 23:50 3.0-pre1 odd behavior Clint Olsen
@ 1996-07-03  4:52 ` Bart Schaefer
  1996-07-03  7:17   ` Never mind (Re: 3.0-pre1 odd behavior) Bart Schaefer
                     ` (2 more replies)
  0 siblings, 3 replies; 7+ messages in thread
From: Bart Schaefer @ 1996-07-03  4:52 UTC (permalink / raw)
  To: Clint Olsen, zsh-workers

On Jul 2,  4:50pm, Clint Olsen wrote:
} Subject: 3.0-pre1 odd behavior
}
} Is this a new feature?
} 
} I've never seen zsh report exit status on jobs in the foreground before.

Happens only with both the `monitor' and `printexitvalue' options set,
and then only for commands that exit nonzero.  I think `printexitvalue'
is a relatively new option, but I'm not sure (I've never set it).

By the way, workers, what's up with `monitor'?

    MONITOR (-m, ksh: -m)
	 Allow job control.  Set by default in interactive shells.

> exec zsh -l
zagzig[21] setopt | grep monitor
monitor             off

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

New male in /home/schaefer:
>N  2 Justin William Schaefer  Sat May 11 03:43  53/4040  "Happy Birthday"



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Never mind (Re: 3.0-pre1 odd behavior)
  1996-07-03  4:52 ` Bart Schaefer
@ 1996-07-03  7:17   ` Bart Schaefer
  1996-07-03 16:30   ` 3.0-pre1 odd behavior Clint Olsen
  1996-07-04 12:04   ` Zoltan Hidvegi
  2 siblings, 0 replies; 7+ messages in thread
From: Bart Schaefer @ 1996-07-03  7:17 UTC (permalink / raw)
  To: zsh-workers

On Jul 2,  9:52pm, Bart Schaefer wrote:
} Subject: Re: 3.0-pre1 odd behavior
}
} By the way, workers, what's up with `monitor'?
} 
} > exec zsh -l
} zagzig[21] setopt | grep monitor
} monitor             off

(Sound of hand smacking forehead)

zagzig[41] setopt >>(grep monitor) ; wait
monitor             on

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

New male in /home/schaefer:
>N  2 Justin William Schaefer  Sat May 11 03:43  53/4040  "Happy Birthday"



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0-pre1 odd behavior
  1996-07-03  4:52 ` Bart Schaefer
  1996-07-03  7:17   ` Never mind (Re: 3.0-pre1 odd behavior) Bart Schaefer
@ 1996-07-03 16:30   ` Clint Olsen
  1996-07-03 17:15     ` Bart Schaefer
  1996-07-04 12:04   ` Zoltan Hidvegi
  2 siblings, 1 reply; 7+ messages in thread
From: Clint Olsen @ 1996-07-03 16:30 UTC (permalink / raw)
  To: zsh-workers

On Tue, 2 Jul 1996 21:52:55 -0700, "Bart Schaefer" writes:
>
> Happens only with both the `monitor' and `printexitvalue' options set,
> and then only for commands that exit nonzero.  I think `printexitvalue'
> is a relatively new option, but I'm not sure (I've never set it).

I am not enabling the printexitvalue or the monitor.  This must be turned
on by default:

~# setopt
allexport
autolist
automenu
bgnice
hashcmds
hashdirs
hashlistall
interactive
login
monitor
notify
printexitvalue
rcexpandparam
shinstdin
zle

-Clint



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0-pre1 odd behavior
  1996-07-03 16:30   ` 3.0-pre1 odd behavior Clint Olsen
@ 1996-07-03 17:15     ` Bart Schaefer
  1996-07-03 17:26       ` Clint Olsen
  0 siblings, 1 reply; 7+ messages in thread
From: Bart Schaefer @ 1996-07-03 17:15 UTC (permalink / raw)
  To: Clint Olsen, zsh-workers

On Jul 3,  9:30am, Clint Olsen wrote:
} Subject: Re: 3.0-pre1 odd behavior
}
} On Tue, 2 Jul 1996 21:52:55 -0700, "Bart Schaefer" writes:
} >
} > Happens only with both the `monitor' and `printexitvalue' options set,
} 
} I am not enabling the printexitvalue or the monitor.  This must be turned
} on by default:

Monitor is on by default for interactive shells, but printexitvalue is
never on by default.

Here's a wild shot in the dark:  How are you starting zsh?

	zsh -l		# Dash-ell, makes zsh a login shell
	zsh -1		# Dash-one, turns on printexitvalue

I could envision someone looking at the FAQ or manual pages in certain
typefaces/fonts and misreading dash-ell as dash-one ...

The only other possibility is that some /etc/zsh* file is setting the
option for you.

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

New male in /home/schaefer:
>N  2 Justin William Schaefer  Sat May 11 03:43  53/4040  "Happy Birthday"



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0-pre1 odd behavior
  1996-07-03 17:15     ` Bart Schaefer
@ 1996-07-03 17:26       ` Clint Olsen
  0 siblings, 0 replies; 7+ messages in thread
From: Clint Olsen @ 1996-07-03 17:26 UTC (permalink / raw)
  To: zsh-workers

On Wed, 3 Jul 1996 10:15:23 -0700, "Bart Schaefer" writes:
>
> 	zsh -l		# Dash-ell, makes zsh a login shell
> 	zsh -1		# Dash-one, turns on printexitvalue
> 
> The only other possibility is that some /etc/zsh* file is setting the
> option for you.

Well, I was doing a setopt -1 to turn on NO_CLOBBER, but apparently the
keybindings have changed!

>From 2.6.beta11:

           NO_CLOBBER (-1)
                Prevents > redirection from truncating existing files.  >!
                may be used to truncate a file instead.  Also prevents >>
                from creating files.  >>! may be used instead.

>From 3.0-pre1:
          PRINT_EXIT_VALUE (-1)
               Print the exit value  of  programs  with  non-zero
               exit status.

It would be nice if the features in ZSH weren't so fluid between versions.

-Clint



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3.0-pre1 odd behavior
  1996-07-03  4:52 ` Bart Schaefer
  1996-07-03  7:17   ` Never mind (Re: 3.0-pre1 odd behavior) Bart Schaefer
  1996-07-03 16:30   ` 3.0-pre1 odd behavior Clint Olsen
@ 1996-07-04 12:04   ` Zoltan Hidvegi
  2 siblings, 0 replies; 7+ messages in thread
From: Zoltan Hidvegi @ 1996-07-04 12:04 UTC (permalink / raw)
  To: schaefer; +Cc: olsenc, zsh-workers

> On Jul 2,  4:50pm, Clint Olsen wrote:
> > exec zsh -l
> zagzig[21] setopt | grep monitor
> monitor             off

Only the last command of a pipe runs in the current shell environment, and
in a subshell monitor is turned off.

But as it already turned out this behaviour was caused by the swap between
-1 and -C.  Every other Bourne-style shell uses -C for noclobber.  It would
be possible to use -C for noclobber only when zsh is invoked as sh/ksh but
that may cause confusion so I decided to make -C noclobber even is zsh
mode.  In zsh scripts only option names shoud be used to turn options
on/off.  Option names will not change and this will make the script more
readable.

Zoltan



^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~1996-07-04 12:19 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1996-07-02 23:50 3.0-pre1 odd behavior Clint Olsen
1996-07-03  4:52 ` Bart Schaefer
1996-07-03  7:17   ` Never mind (Re: 3.0-pre1 odd behavior) Bart Schaefer
1996-07-03 16:30   ` 3.0-pre1 odd behavior Clint Olsen
1996-07-03 17:15     ` Bart Schaefer
1996-07-03 17:26       ` Clint Olsen
1996-07-04 12:04   ` Zoltan Hidvegi

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).