zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: _history_complete_{newer,older} complains on "unmat ched" in _all_labels if globbing
Date: Tue, 21 Oct 2014 23:43:53 -0700	[thread overview]
Message-ID: <141021234353.ZM14828@torch.brasslantern.com> (raw)
In-Reply-To: <5446CB4F.7080808@gmail.com>

On Oct 22,  3:08am, Vasiliy Ivanov wrote:
} 
} % typeset -a somevariable
} % somevariable=(1 2 3)
} 
} % *mevar<_history-complete-older> (completed properly, 2 items suggested - 'somevariable=(' and
} 'somevariable', guessed because expand prefix suffix style)
} 
} but fires hundreds of messages:
} _all_labels:39: closing brace expected
} ...
} _all_labels:39: unmatched '
} ...
} _all_labels:39: unmatched "
} 
} reproducible with any globbing syntax, zsh 5.0.7

There's something else about your configuration that you're not telling
us, because I can't get any completions at all for *mevar unless I
"setopt globcomplete", and I don't get any error messages even with
that set.

Line 39 of _all_labels is

    "${(@)argv[4,__pre]}" "${(P@)2}" "${(@)argv[__suf,-1]}" && __ret=0

which ends up substituting into something like

     +_all_labels:39> compadd -1 -V -default- -X '%SCompleting %Uhistory word%u%s' -Q -a 'historywords[beg,beg+slice]'
     +_all_labels:39> __ret=0 

(though in your case the assignment to __ret is likely not happening)


  reply	other threads:[~2014-10-22  6:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 21:08 _history_complete_{newer,older} complains on «unmatched» " Vasiliy Ivanov
2014-10-22  6:43 ` Bart Schaefer [this message]
2014-10-22  8:53   ` _history_complete_{newer,older} complains on "unmat ched" " Vasiliy Ivanov
2014-10-22 11:08     ` Daniel Shahaf
2014-10-22 21:26       ` Vasiliy Ivanov
2014-10-23  3:18         ` Bart Schaefer
2014-10-24 20:47           ` Vasiliy Ivanov

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=141021234353.ZM14828@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).