zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Clint Olsen <olsenc@ichips.intel.com>, zsh-workers@math.gatech.edu
Subject: Re: 3.0-pre1 odd behavior
Date: Wed, 3 Jul 1996 10:15:23 -0700	[thread overview]
Message-ID: <960703101524.ZM1808@candle.brasslantern.com> (raw)
In-Reply-To: Clint Olsen <olsenc@ichips.intel.com> "Re: 3.0-pre1 odd behavior" (Jul  3,  9:30am)

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"



  reply	other threads:[~1996-07-03 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-02 23:50 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 [this message]
1996-07-03 17:26       ` Clint Olsen
1996-07-04 12:04   ` Zoltan Hidvegi

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=960703101524.ZM1808@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=olsenc@ichips.intel.com \
    --cc=schaefer@nbn.com \
    --cc=zsh-workers@math.gatech.edu \
    /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).