From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 12292 invoked from network); 15 Jun 2020 05:10:13 -0000
Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2)
  by inbox.vuxu.org with ESMTPUTF8; 15 Jun 2020 05:10:13 -0000
Received: (qmail 5985 invoked by alias); 15 Jun 2020 05:09:59 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
List-Unsubscribe: <mailto:zsh-users-unsubscribe@zsh.org>
X-Seq: 24933
Received: (qmail 8870 invoked by uid 1010); 15 Jun 2020 05:09:59 -0000
X-Qmail-Scanner-Diagnostics: from mail-oi1-f173.google.com by f.primenet.com.au (envelope-from <schaefer@brasslantern.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.102.3/25842. spamassassin: 3.4.4.  
 Clear:RC:0(209.85.167.173):SA:0(-1.9/5.0):. 
 Processed in 1.739718 secs); 15 Jun 2020 05:09:59 -0000
X-Envelope-From: schaefer@brasslantern.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.167.173 as permitted sender)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=Mmoc7TBwZTe8lOV5pTBIXZwEVRZswexoCAGARzLPrLQ=;
        b=LCGdxaoxJniCVYYNX8jy+BA+jjIhnqTEW/xdJmJqFw6n0r9SE2zymBiIpSz4I7Umj+
         tEQ1FRcpk9UGGo1mimnPUwU6uA3kFxYKYK/fClYiEGqZA9IiSQqZHZ8puOaGN/Qb5d13
         hn2wLAQxveZpFFy56CmiNBFyJID+12vilJ2Rxy5Nr1x/aINVQzRj1YVHMzeyNPQsKtEL
         XVpRVPoY4SNgUEcaoDGUxN4bfBcI/D5dwJuHfuEjbhVhQyhyT8FJFCdMsON3UwxtN0lP
         YqNBhGSRfVDoSbb4TCSE+Ds9NHVCIXUjFOjd6qO1MoMNdYSMrygKhNW6kFfF1VYMdvS4
         BbjQ==
X-Gm-Message-State: AOAM5339ZxrJ8NSnO7QHTbPWuycDgwB1h0RwGd102pMbPFgRSigwbt/+
	JVjx0EzJQ+vOO7LDb3omrgYkOJogI/NqoIV7K+FnWQ==
X-Google-Smtp-Source: ABdhPJw8aevxNB42/dnpbpZQdrjA5GSBxWSwWFw9KfnW2Yr74ZnasctJuYYtl789THKNCh2HugBoTb5Q9nJzZKrwv0Q=
X-Received: by 2002:aca:cf15:: with SMTP id f21mr7576451oig.173.1592197763432;
 Sun, 14 Jun 2020 22:09:23 -0700 (PDT)
MIME-Version: 1.0
References: <CAL7A0-P6qmPidGHiYy6=1jmUY6T=X4xktbp1Wv2CBO0CX2xJRQ@mail.gmail.com>
 <CAH+w=7Z8F5-9g2isMha2B0gUU-fVYirezaEWr1AnupQRep6A6A@mail.gmail.com>
 <CAL7A0-NSfM7fRZS4491teaUJGBkQW46RC+JtwS7PtHM4RX1mPg@mail.gmail.com>
 <CAL7A0-POtHWPReN0Z3z+Z7x7+1=aa+WfXvozKex=-mzJr0mQJQ@mail.gmail.com>
 <CAH+w=7aR_BjcWsfRZOtSas+r9zHphf12-2f=-C0CYZHZ4b3gCg@mail.gmail.com>
 <CAL7A0-PMSV6ZM5USa55mfH4=xaV0heCL7Uqe31B8RJxcgTBWjg@mail.gmail.com>
 <CAH+w=7Y1gnTGA0hWf7o5ffTdor17EQE1PTGe_YrqkxvWGk72rQ@mail.gmail.com>
 <CAL7A0-Mye7pcAVdhFT0tcc3XAoHOokY7qAQqo-tgN=bs1cNPOw@mail.gmail.com> <CAH+w=7aiQNO+-1EG2EyrH0JAMienH+aLQ+k9O27E8eTD0RmJFg@mail.gmail.com>
In-Reply-To: <CAH+w=7aiQNO+-1EG2EyrH0JAMienH+aLQ+k9O27E8eTD0RmJFg@mail.gmail.com>
From: Bart Schaefer <schaefer@brasslantern.com>
Date: Sun, 14 Jun 2020 22:09:12 -0700
Message-ID: <CAH+w=7bm21k8s9VsNvYdQrK+ReSFk=UViM4_29EHTcTPrDYZXw@mail.gmail.com>
Subject: Re: menu-select doesn't respect COMPLETE_IN_WORD option
To: Alan <8fvebtoeq87@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Content-Type: text/plain; charset="UTF-8"

On Sun, Jun 14, 2020 at 5:37 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Sat, Jun 13, 2020 at 9:28 PM Alan <8fvebtoeq87@gmail.com> wrote:
> >
> > When I leave completeinword unset, _prefix completion simply doesn't work, even if I have:
>
> If I turn on "completeinword" then I can reproduce your described
> behavior with menu-complete, although expand-or-complete-prefix still
> works as expected. [...]
>
> So I still think you want to leave complete-in-word turned off and
> find out what other part of your startup is breaking things when you
> do.

Ignore that last part, sorry.  I just realized that when you wrote
"_prefix completion simply doesn't work" you did not mean that
completion failed, you just mean that it did something you didn't want
it to, and that "something" is probably exactly what I described it
doing.

This documentation is in fact correct: "One gotcha with the _prefix
completer: you have to make sure the option COMPLETE_IN_WORD is set."