zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zefram <A.Main@dcs.warwick.ac.uk>
Cc: zsh-workers@math.gatech.edu
Subject: Re: zsh-3.0-pre4 released
Date: Sat, 27 Jul 1996 13:38:34 -0700	[thread overview]
Message-ID: <960727133834.ZM26853@candle.brasslantern.com> (raw)
In-Reply-To: Zefram <A.Main@dcs.warwick.ac.uk> "Re: zsh-3.0-pre4 released" (Jul 27,  9:02pm)

On Jul 27,  9:02pm, Zefram wrote:
} Subject: Re: zsh-3.0-pre4 released
}
} I've been using the `new options' (slightly) longer than anyone else
} (how's that for brag value :-)), and while I agree that it is initially
} a little disconcerting, I find that I prefer the cleaner setopt output.

Cleaner?  Like I said, the baseline behavior should be what happens when
all the options are unset.  The cleanest output is none at all.

} I also find that the testing of options is a little clearer in
} general, in the code.  (The option patch actually normalised all option
} tests to either isset(FOO) or unset(FOO).)
} 
} I do prefer unset(UNSET) to isset(NOUNSET).

There's nothing that requires us to use NOUNSET in the code.  You yourself
used EXECOPT instead of EXEC, for example (and for obvious reasons).

} >                                                    Why shouldn't "nohup"
} >parallel the command prefix of the same name?
} 
} It does.

"setopt nohup" parallels it, but the output of "setopt" doesn't say "nohup".

} >At least with the NO_ prefix, you could tell that there is some expected
} >behavior that is being modified.
} 
} True, that's how the options used to work, but what is the "expected
} behaviour"?  It varies depending on whether we're emulating sh, ksh,
} csh, zsh, (when we get round to it) POSIX, or whatever.

The "expected behavior" is what you get when you run "./zsh" out of
the build directory on a machine that's never had zsh near it before.

Emulations are just that; they're by definition not baseline behavior
(unless what you're writing is nothing more than an emulator).

] Not to mention
} that not even all the non-special options defaulted to off anyway

The only ones that didn't are FUNCTION_ARGZERO, which is new; BG_NICE,
which has always annoyed me anyway (and which originally didn't default
that way, if I recall correctly); and the three HASH options, which
don't change any user-visible behavior, only performance tradeoffs.

-- 
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-27 20:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199607270206.EAA04563@hzoli.ppp.cs.elte.hu>
1996-07-27  4:30 ` Bart Schaefer
1996-07-27 15:55   ` Zoltan Hidvegi
1996-07-27 18:35     ` Bart Schaefer
1996-07-27 22:06       ` Zoltan Hidvegi
1996-07-27  4:57 ` Bart Schaefer
1996-07-27 17:03   ` Zefram
1996-07-27 19:26     ` Bart Schaefer
1996-07-27 20:02       ` Zefram
1996-07-27 20:38         ` Bart Schaefer [this message]
1996-07-27 22:27   ` Zoltan Hidvegi
1996-07-30  2:22 ` Clive Messer
1996-07-30 12:18   ` Clive Messer

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=960727133834.ZM26853@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=A.Main@dcs.warwick.ac.uk \
    --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).