zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: emulate (Re: Prompt fun)
Date: Thu, 7 Oct 1999 17:20:15 +0000	[thread overview]
Message-ID: <991007172015.ZM27237@candle.brasslantern.com> (raw)
In-Reply-To: <E11ZFoG-0001Nn-00@crucigera.fysh.org>

On Oct 7,  4:50pm, Zefram wrote:
} Subject: Re: PATCH: emulate (Re: Prompt fun)
}
} Bart Schaefer wrote:
} >Hmm.  I tend to think of it exactly the opposite way -- if I set errexit,
} >I generally want it to continue to apply down through functions I call,
} >because of exactly the circumstances you note -- scripts run from make,
} >which uses -e when it invokes the shell.
} 
} Hmm.  Surely in that case, the functions in question are going to be ones
} written to be executed in the context of that particular script, and
} will be intended to have ERR_EXIT set, and won't have an emulate line?

The function might be written so that zsh executes it as an autoload but
bash runs it as a separate script process.  In the former case, an emulate
might be required.

However, I admit that there is merit in your argument; it's just that I
tend to want to resolve conflicts by *not* changing existing behavior ...

Which reminds me:  I believe the original intent of "emulate" was not to
reset _all_ options that might affect parsing (unless "emulate -R" is
used).  I believe the intent was to reset any option that would confuse
a ksh or sh script running in zsh.  Options like "cdablevars" and "autocd"
were *not* handled by "emulate" because no reasonable ksh script could
possibly depend upon those behaviors, nor could a correctly-working ksh
script use syntax that could accidentally trigger them.

Scripts that need to port among different users' zsh configurations, as
opposed to porting zsh<->ksh, were supposed to use "emulate -R" and then
setopt exactly the options they needed.

Perhaps the situation has changed enough, now that large parts of the zsh
distribution are written as zsh scripts, that we should revisit that and
make most of the changes in Zefram's patch.  On the other hand, I'm as
usual loathe to make "silent" changes to the option semantics.  I'd much
rather see an additional flag to "emulate" that catches these additional
problem cases.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1999-10-07 17:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-07  0:28 PATCH: Re: Prompt fun Bart Schaefer
1999-10-07 10:41 ` PATCH: emulate (Re: Prompt fun) Zefram
1999-10-07 14:53   ` Bart Schaefer
1999-10-07 15:11     ` Zefram
1999-10-07 15:42       ` Bart Schaefer
1999-10-07 15:50         ` Zefram
1999-10-07 17:20           ` Bart Schaefer [this message]
1999-10-07 17:29             ` Zefram
1999-10-07 18:56               ` Bart Schaefer
1999-10-08  9:58                 ` Zefram
1999-10-07 20:32               ` Reasons for not wanting EXTENDED_GLOB interactively (was Re: PATCH:...) Bruce Stephens
1999-10-08  6:15                 ` Andrej Borsenkow
1999-10-10 23:03   ` PATCH: Re: PATCH: emulate (Re: Prompt fun) Bart Schaefer
1999-10-10 23:19     ` Bart Schaefer
1999-10-11  8:20       ` Zefram
1999-10-10 23:21     ` Bart Schaefer
1999-10-11  8:17       ` Zefram

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=991007172015.ZM27237@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).