zsh-workers
 help / color / mirror / code / Atom feed
From: Richard Coleman <coleman@math.gatech.edu>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu (zsh-workers)
Subject: Re: Octal interpretation
Date: Fri, 03 Nov 1995 20:28:34 -0500	[thread overview]
Message-ID: <199511040128.UAA09251@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Fri, 03 Nov 1995 17:54:53 +0100." <199511031654.RAA08852@bolyai.cs.elte.hu>

> I think 0xff hexadecimal notation can be kept but the octal notation should be
> removed.  My releases do this.  It would not be difficult to implement it in
> the baseline.  My patch only works together with the other bugfixes and
> cleanups I made in math.c.  Richard, is there any reason you do not add my
> fixes to the baseline?  I try to keep them uptodate.  I provide RCS file which
> contains all of the patches separately.  I have tools which makes merging the
> patches easier.  Several people complaind recently about bugs which I fixed
> long ago.  I completely cleaned up the lexer and the substitution code.
> Without the substitution fixes zsh cannot be installed as /bin/sh (e.g. the
> common ${1+"$@"} sh idiom does not work with more than one arguments).  Some
> developers also expressed interest in rewriting the lexer to achieve 8bit
> compilance.  I think the baseline lexer is a wrong starting point.  The
> modified lexer supports completion which makes get_comp_string() in
> zle_tricky.c much simpler (that was the most horrible zle function in
> zle_tricky).  I do not really care about the new features I added.  All of
> them are very minor (but they are well tested by now, since many people used
> my releases for more than a half year now).  I do not like this state.  Now a
> significant amount of my time is spent on kepeng the patches up-to-date.  And
> by now there are many patches from other people which did not find their way
> to the baseline but are very essential.

It's just an artifact of the way I do things.  I have a one track
mind and tend to do things serially.  First I worked on configure
and the Makefiles.  This lead me to start working on the signals code
(for portability).  This lead me to start working on the hashtable.c.
>From there is was builtin.c (which I actually rewrote a substantial part
of) and then exec.c.  The work on exec.c has started me thinking about
subst.c, so I will probably begin integrating some of these patches.

I realize I'm slow at this, but I try to be very meticulous when I
integrate changes into the baseline.  I usually check over every patch
line by line.  I had to start doing this, because people were sending
in patches without understanding all the implications of the changes
they were making.  This is understandable since parts of zsh are very
complicated.  This way of doing things has slowed down progress somewhat,
but will ultimately produce a much better zsh.

Also, it is time consuming for me to go through the RCS files from your
distribution.  It would be a big help if you started e-mailing me some
of the pieces you think are the most essential.

rc


      reply	other threads:[~1995-11-04  1:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-11-03  9:01 Peter William Stephenson
1995-11-03 10:58 ` Richard Coleman
1995-11-03 16:54   ` Zoltan Hidvegi
1995-11-04  1:28     ` Richard Coleman [this message]

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=199511040128.UAA09251@redwood.skiles.gatech.edu \
    --to=coleman@math.gatech.edu \
    --cc=hzoli@cs.elte.hu \
    --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).