zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Jens Elkner <jel+zsh@cs.uni-magdeburg.de>, zsh-workers@zsh.org
Subject: Re: 5.3.1 - lot of bad math expression
Date: Mon, 16 Jan 2017 17:48:52 +0000	[thread overview]
Message-ID: <20170116174852.079e7833@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20170116172250.GA17611@trex.cs.ovgu.de>

On Mon, 16 Jan 2017 18:22:50 +0100
Jens Elkner <jel+zsh@cs.uni-magdeburg.de> wrote:
> when trying to find a solution/propper settings for the
> X=./{etc,bin} ; ls $X   problem I decided to give the latest release aka
> 5.3.1 a try. However, here I get a lot of errors wrt. the default
> completion files e.g. for ls\t like:
> 
> _arguments:360: bad math expression: operator expected at `descrs'
> _main_complete:341: bad math expression: operator expected at
> `lastdescr'
> _main_complete:380: bad math expression: operator expected at
> `comp_color...'

Looks like that's the POSIX_IDENTIFIERS option.

The _comp_options arrays is there to try to limit option changes so that
most user options percolate through into the completion code.  The
trouble is, as you've discovered, this doesn't really work.

pws

diff --git a/Completion/compinit b/Completion/compinit
index 2715c47..cc663cb 100644
--- a/Completion/compinit
+++ b/Completion/compinit
@@ -154,6 +154,7 @@ _comp_options=(
     NO_markdirs
     NO_octalzeroes
     NO_posixbuiltins
+    NO_posixidentifiers
     NO_shwordsplit
     NO_shglob
     NO_warncreateglobal


  reply	other threads:[~2017-01-16 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170116172413epcas2p175e693f3a2c0949043f4edaa7c67158f@epcas2p1.samsung.com>
2017-01-16 17:22 ` Jens Elkner
2017-01-16 17:48   ` Peter Stephenson [this message]
2017-01-16 18:38     ` Jens Elkner

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=20170116174852.079e7833@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --cc=jel+zsh@cs.uni-magdeburg.de \
    --cc=zsh-workers@zsh.org \
    /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).