From: Zefram <zefram@dcs.warwick.ac.uk>
To: pws@ifh.de (Peter Stephenson)
Cc: zsh-workers@math.gatech.edu
Subject: Re: zle_refresh trial patch (and unrelated bug)
Date: Thu, 14 Nov 1996 14:57:15 +0000 (GMT) [thread overview]
Message-ID: <22303.199611141457@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <199611140903.KAA16132@hydra.ifh.de> from "Peter Stephenson" at Nov 14, 96 10:03:34 am
> Anything more
>sophisticated probably needs (( to have it's own type flag in struct
>Cmd.
I for one would like that to happen. It's really annoying to have (())
changed to let when listing functions. It's also confusing to have
(()) fail after "disable let".
>(Sorrysorry... it's against 3.1 again. I don't have the luxury here
>of space for arbitrary versions. I really don't think that will make
>a difference this time.)
It only really makes a difference when patching the module code
itself. IMO we shouldn't be posting patches for `configure' itself
anyway; they are large and contain no information. (zsh developers can
be assumed to have autoconf available.)
-zefram
next prev parent reply other threads:[~1996-11-14 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-08 15:26 Handling for ZLE modules Peter Stephenson
[not found] ` <pws@ifh.de>
1996-11-08 16:45 ` Bart Schaefer
1996-11-11 16:02 ` Bart Schaefer
1996-11-13 18:53 ` zle_refresh trial patch (and unrelated bug) Bart Schaefer
1996-11-14 9:03 ` Peter Stephenson
1996-11-14 14:57 ` Zefram [this message]
1996-11-08 17:16 ` Handling for ZLE modules Zefram
1996-11-08 17:26 ` Bruce Stephens
1996-11-10 23:55 ` Zoltan Hidvegi
1996-11-11 13:07 ` Peter Stephenson
1996-11-09 10:22 zle_refresh trial patch Geoff Wing
[not found] ` <gwing@primenet.com.au>
1996-11-09 17:09 ` zle_refresh trial patch (and unrelated bug) Bart Schaefer
1996-11-12 12:40 ` Peter Stephenson
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=22303.199611141457@stone.dcs.warwick.ac.uk \
--to=zefram@dcs.warwick.ac.uk \
--cc=pws@ifh.de \
--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).