help / color / mirror / code / Atom feed
From: Marlon Richert <marlon.richert@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Peter Stephenson <p.w.stephenson@ntlworld.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] COMPLETE_IN_WORD fails to recognize brace_parameter context
Date: Sat, 8 May 2021 16:04:36 +0300	[thread overview]
Message-ID: <F56F0B4D-35D2-4161-8A77-E3FF83D7694E@gmail.com> (raw)
In-Reply-To: <CAH+w=7ajH4H9eJwB5=jEGm77VZXhRGD5h53wT7Un=py8jeb-dg@mail.gmail.com>

On 8 May 2021, at 03:04, Bart Schaefer <schaefer@brasslantern.com> wrote:
>> This works correctly:
>> % setopt completeinword
>> % tst() { print "\n$compstate[context]"; zle -I }
> I think there's something missing here for the test case.  A style or
> a bindkey?  Something to run "tst"?

Ah, yes. I apparently forget to add:

% zle -C tst complete-word tst
% bindkey '^I' tst

But it looks like you figured out the gist of it anyway. :)

  reply	other threads:[~2021-05-08 18:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 14:37 Bug report: Completion for dynamically named dirs fails when $SUFFIX is not empty Marlon Richert
2021-01-25 15:07 ` Peter Stephenson
2021-03-31  8:10   ` Marlon Richert
2021-03-31  8:25     ` Peter Stephenson
2021-03-31  8:29       ` Marlon Richert
2021-03-31  8:37         ` Marlon Richert
2021-03-31  8:56           ` Peter Stephenson
2021-05-07 14:08   ` [BUG] COMPLETE_IN_WORD fails to recognize brace_parameter context Marlon Richert
2021-05-08  0:04     ` Bart Schaefer
2021-05-08 13:04       ` Marlon Richert [this message]
2021-05-08  4:37     ` Bart Schaefer
2023-02-22 11:55   ` Bug report: Completion for dynamically named dirs fails when $SUFFIX is not empty Marlon Richert

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F56F0B4D-35D2-4161-8A77-E3FF83D7694E@gmail.com \
    --to=marlon.richert@gmail.com \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \


* 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


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).