From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zefram <zefram@fysh.org>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: emulate (Re: Prompt fun)
Date: Thu, 7 Oct 1999 14:53:47 +0000 [thread overview]
Message-ID: <991007145347.ZM27050@candle.brasslantern.com> (raw)
In-Reply-To: <E11ZAyr-0005J7-00@crucigera.fysh.org>
On Oct 7, 11:41am, Zefram wrote:
} Subject: PATCH: emulate (Re: Prompt fun)
}
} Bart Schaefer wrote:
} > emulate -L zsh
} >+ setopt extendedglob
}
} This shouldn't be causing confusion. emulate is supposed to set all
} (and only) the options that can affect the behaviour of a script.
} The patch below fixes this.
I disagree with a number of these changes, particularly promptbang,
promptpercent, and promptsubst. Most scripts do not alter the values
of PS[1234], and resetting the prompt-expansion options will cause the
user's settings to display as garbage in conjunction with either use
of "select" loops or (as of 3.1.6) "setopt xtrace"/"set -x".
I further think it's unwise to have emulate reset either errexit or
"exec" -- though I don't see how it could possibly make any difference
to the latter, as emulate itself won't be executed if exec isn't set.
I don't have any really strong feelings about the others, though there
may be room for some debate as to how many of them are "likely to cause
portability problems in scripts and functions." Certainly I agree with
some of the changes, e.g. the history options ought *not* to be reset.
} The patch quoted above is still necessary; EXTENDED_GLOB is unset
} by default even in zsh mode. Would changing that break any scripts?
Yes, it would break some of my scripts.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-10-07 14:54 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 [this message]
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
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=991007145347.ZM27050@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zefram@fysh.org \
--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).