From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Phil Pennock <comet@fysh.org>,
Zsh Development Workers <zsh-workers@math.gatech.edu>
Subject: Re: 3.0.5 patches
Date: Wed, 6 Jan 1999 08:40:28 -0800 [thread overview]
Message-ID: <990106084028.ZM14163@candle.brasslantern.com> (raw)
In-Reply-To: <19990106101741.A15834@fysh.org>
On Jan 6, 10:17am, Phil Pennock wrote:
} Subject: 3.0.5 patches
}
} How many current patches are there against 3.0.5?
}
} Bart refered in one article to 3.0.5-extended -- is that local to you
} Bart? A search on the web-site archives turns up nothing.
You'll find it if you search the zsh-users archive with partial word
matching turned on, for the string 3.0.5-extended . It's a bit out of
date now.
} I'm thinking of creating a megapatch. The list I currently have is:
} Archive# Details
} 3548(1997) Zoltan - rcexpandparam
} 1880 Bart - handling EINTR with command substitutions
} 4644 Bart - arithmetic expressions
} 4870 Goran Larsson - Y2k
} 3809 Bart (3.0.5 adapt of PWS 3.1.x patch) - Glob qualifier close
} 4447 Bart - (believe sigwinch)
There's a lot more than that in the -extended patch, though the 4xxx
ones aren't there.
} I know that this last patch might be objected to - I'd go on opinion
} here. Or am I just duplicating what someone else has already done?
There was talk at about the time 3.1.5 popped out of doing an official
3.0.6. Here's a summary of the patches to 3.0.5 I have in my CVS tree,
most of which was sent to Zefram back in October; I don't know all the
article numbers:
----------------
The HIST_REDUCE_BLANKS option.
PWS's "preexec" function (ala "precmd"), from zsh-users 1068.
Andreas J. Koenig's patch from zsh-workers 3660 to cause failure of rlimits.awk
to properly abort the build.
PWS's patch from zsh-workers 3526 to permit history commands (fc and r) to be
used in command substitutions ($() and ``).
Patch readoutput() so the output of command substitutions isn't lost on an
EINTR read error, from zsh-users 1880.
PWS's patch from zsh-workers 3808 for (:s/x/y) glob qualifiers.
PWS's patch for number-range globbing with number-prefix matching.
PWS's patch from zsh-workers 4172 to eliminate the `lastc' global and thereby
clean up some goofy history management and a couple of unexpected exits.
PWS's patch for mishandled job wait when the last job in a pipeline is not
added to the job table before an earlier job in the same pipeline is reaped,
from zsh-workers 4397.
PWS's patch from zsh-workers 3818 to not mess up the tty settings when doing
a command while zle is active (e.g. inside a completion function).
Zoltan's patch from zsh-workers 3974 for crash on unset of a special param.
Adaptation to 3.0.5 of Zoltan's patch from zsh-workers 4376 for case ... esac
parsing; any single complex command should parse as if semicolon-terminated.
PWS's patch from zsh-workers 3806 for ${var:s/x/y} modifiers.
Zoltan's patch for rcexpandparam bug, from zsh-workers 3548.
Zefram's chaselinks patch from zsh-workers 3872.
Don't call ioctl(TIOCSWINSZ) from non-interactive shells.
PWS's patch from zsh-workers 3816 for bindkey exiting too vigorously on error.
Sven's patch from 4148 for starting menucompletion when the inserted prefix
would otherwise trigger REC_EXACT.
Sven's patch from 4147 for strange completinword behavior.
Sven Wischnowsky's patch from zsh-workers 4140 for starting menu completion
following a compctl that uses -U.
PWS's patch to simplify expand-or-complete-prefix.
Wayne Davison's patch from zsh-workers 3969 for positioning the mark after
a yank.
PWS's helpfiles revision, from zsh-workers 3598.
PWS's tweak from zsh-workers 4612 that seems to fix signed char problems
which in turn break input of chars with the high bit set.
Fix (for unspecified problem) from Sven in zsh-workers 4697.
Fix strange cursor placement following vi-oper-swap-case.
Cross end-of-line in vi-forward-word when editing multiple lines.
Fix for ${(l<10><x>)foo} and ${(l<10><0><x>)foo} from zsh-workers 4644.
----------------
I'm not actually running the resulting version on a regular basis (mainly
because I'm too lazy/distracted to install it). Hmm, it appears I never
committed the SIGWINCH change, probably because I don't have trouble with
it.
I could generate a patch for all of that pretty easily, though I also have
a couple of local changes that I'd have to excise. However, I'd rather not
do it if Zefram is going to surface and release 3.0.6 pretty soon.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-01-06 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-06 10:17 Phil Pennock
1999-01-06 16:40 ` Bart Schaefer [this message]
1999-01-06 16:53 ` Phil Pennock
1999-01-10 7:24 ` 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=990106084028.ZM14163@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=comet@fysh.org \
--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).