zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Alexey Tourbin <at@altlinux.ru>, zsh-workers@sunsite.dk
Subject: Re: compaudit problem
Date: Sat, 19 Aug 2006 10:30:33 -0700	[thread overview]
Message-ID: <060819103035.ZM28413@torch.brasslantern.com> (raw)
In-Reply-To: <20060819115030.GE25959@localhost.localdomain>

On Aug 19,  3:50pm, Alexey Tourbin wrote:
}
} compaudit:50: bad substitution

That would be on this line:

  local _compdir=${fpath[(r)*/$ZSH_VERSION/*]}

} compinit:469: bad pattern: _i_test[=yes

Interesting; that's on:

      _i_test[$_i_name]=yes

} colors:39: bad substitution

Maybe zsh has a problem with function names that begin with "co". :-)
Seriously, this is pretty clearly a problem with subscript parsing.

for k in ${(k)color}; do color[${color[$k]}]=$k; done

} The error messages are issued at zsh startup.  4.3.2-20060619 snapshot
} did not have such a problem.

In all cases the parse of the subscript appears to have run one byte
too far and consumed the ']'.  What operating system and compiler are
you using?

I can't reproduce any of these with my build of 08/17 sources from CVS.
I've tried compiling both with and without multibyte support.  I've even
tried forcing Test/D07multibyte.ztst to use ru_RU.UTF-8 as $LANG when
running "make check".

Does anything change if you run "zsh -o posix_identifiers"?  Have you
tried building with "configure --disable-multibyte"?

Changes between 06/19 and 07/29 that may have affected this:

        * 22518: Src/params.c, Src/utils,c, Src/zsh.h,
        Test/B02typeset.ztst: Initial go at making parameter subscripts
        use multibyte characters.

        * 22524: Src/params.c, Test/D07multibyte.ztst: searchable
        subscripts with multibyte characters.

        * 22544: README, Doc/Zsh/options.yo, Src/builtin.c, Src/glob.c,
        Src/lex.c, Src/math.c, Src/module.c, Src/options.c, Src/params.c,
        Src/parse.c, Src/subst.c, Src/utils.c, Src/zsh.h, Src/ztype.h,
        Src/Zle/compcore.c, Src/Zle/zle_tricky.c, Test/D07multibyte.ztst:
        Improve use of ztype tests for multibyte characters.  Add
        POSIX_IDENTIFIERS option to control allowability of multibyte
        alphanumeric characters in parameter and module names.

        * 22556: Doc/Zsh/builtins.yo, Functions/Zle/insert-composed-char,
        Src/builtin.c, Src/pattern.c, Src/subst.c, Src/utils.c, Src/zsh.h,
        Src/ztype.h, Src/Zle/zle.h, Src/Zle/zle_main.c,
        Test/D04parameter.ztst, Test/D07multibyte.ztst: Multibyte
        separators and delimiters.

        * unposted: Src/pattern.c, Src/utils.c: minor typos in
        22556 found when MULTIBYTE_SUPPORT is not defined.

        * 22557: Doc/Zsh/options.yo, Misc/globtests, Src/options.c,
        Src/pattern.c, Test/D02glob.ztst, Test/D07multibyte.ztst:
        Turn on multibyte option by default for MULTIBYTE_SUPPORT and fix
        tests and patterns.


-- 


  reply	other threads:[~2006-08-19 18:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-19 11:50 Alexey Tourbin
2006-08-19 17:30 ` Bart Schaefer [this message]
2006-08-19 17:45   ` Alexey Tourbin
2006-08-19 19:20     ` Bart Schaefer
2006-08-20 17:55       ` Alexey Tourbin
2006-08-19 18:00   ` Alexey Tourbin
2006-08-20 17:16     ` Peter Stephenson
2006-08-20 17:32       ` Alexey Tourbin
2006-08-20 18:33         ` Peter Stephenson
2006-10-17 19:05   ` Alexey Tourbin
2006-10-18  3:41     ` Bart Schaefer
2006-10-18 12:00       ` Alexey Tourbin
2006-10-18 13:31         ` Peter Stephenson
2006-10-18 16:20           ` Alexey Tourbin
     [not found]             ` <20061018182019.62809029.pws@csr.com>
2006-10-19  0:17               ` Alexey Tourbin
2006-10-19  8:35                 ` 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=060819103035.ZM28413@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=at@altlinux.ru \
    --cc=zsh-workers@sunsite.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).