From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu
Subject: 3.0.1-test2 - patch for Functions/
Date: Thu, 26 Sep 1996 09:42:09 -0700 [thread overview]
Message-ID: <960926094209.ZM13235@candle.brasslantern.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "Re: emacs configure broken when invoked as /bin/sh" (Sep 24, 1:40am)
This adds "emulate -R zsh" to autoload functions from Functions/ whose
behavior may be affected by starting zsh as ksh (they use arrays, mainly).
Index: Functions/cdmatch
*** zsh-3.0.0/Functions/cdmatch Mon May 6 07:08:56 1996
--- zsh-3.0.0-build/Functions/cdmatch Sun Aug 18 10:09:24 1996
***************
*** 6,14 ****
# Completes directories for cd, pushd, ... anything which knows about cdpath.
# You do not have to include `.' in your cdpath.
#
! # It works properly only if $ZSH_VERSION > 2.6-beta2. For erarlier versions
# it still works if RC_EXPAND_PARAM is not set or when cdpath is empty.
!
local narg pref cdp
read -nc narg
--- 6,16 ----
# Completes directories for cd, pushd, ... anything which knows about cdpath.
# You do not have to include `.' in your cdpath.
#
! # It works properly only if $ZSH_VERSION > 3.0-pre4. Remove `emulate -R zsh'
! # for all other values of $ZSH_VERSION > 2.6-beta2. For earlier versions
# it still works if RC_EXPAND_PARAM is not set or when cdpath is empty.
! emulate -R zsh
! setopt localoptions
local narg pref cdp
read -nc narg
Index: Functions/cdmatch2
*** zsh-3.0.0/Functions/cdmatch2 Sat May 4 17:39:32 1996
--- zsh-3.0.0-build/Functions/cdmatch2 Sun Aug 18 10:11:14 1996
***************
*** 1,6 ****
--- 1,8 ----
# This function should be called from compctl to complete the
# second argument of cd and pushd.
+ emulate -R zsh # Requires zsh 3.0-pre4 and later
+ setopt localoptions
local from
read -Ac from
Index: Functions/multicomp
*** zsh-3.0.0/Functions/multicomp Fri Aug 2 10:36:08 1996
--- zsh-3.0.0-build/Functions/multicomp Sun Aug 18 10:13:38 1996
***************
*** 14,19 ****
--- 14,20 ----
# Liable to screw up escaped metacharacters royally.
# $fignore is not used: feel free to add your own bit.
+ emulate -R zsh # Requires zsh 3.0-pre4 or later
local pref head sofar origtop newtop globdir="(-/)" wild
setopt localoptions nullglob rcexpandparam globdots
unsetopt markdirs globsubst shwordsplit nounset
--
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"
next prev parent reply other threads:[~1996-09-26 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-23 21:11 emacs configure broken when invoked as /bin/sh Benjamin Lorenz
1996-09-23 23:40 ` Zoltan Hidvegi
1996-09-26 16:42 ` Bart Schaefer [this message]
1996-09-26 16:56 ` 3.0.1-test2 - sanity for COLUMNS, LINES, FIGNORE, MAILPATH, and PSVAR Bart Schaefer
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=960926094209.ZM13235@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=hzoli@cs.elte.hu \
--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).