From: Vin Shelton <acs@alumni.princeton.edu>
To: Jun T <takimoto-j@kba.biglobe.ne.jp>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Y01 Test Failure on Arch
Date: Sat, 3 Apr 2021 07:32:17 -0400 [thread overview]
Message-ID: <CACeGjnVQamQM0r4d45CAHTOq=vERpQwiDUV0_SaKm_Ey_D+bPg@mail.gmail.com> (raw)
In-Reply-To: <A36DEE01-E038-4F5C-91E6-1B2972E3487F@kba.biglobe.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
Ping. The failure still occurs.
HTH,
Vin
On Thu, Apr 1, 2021 at 12:05 AM Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
>
> > 2021/03/31 22:40, Vin Shelton <acs@alumni.princeton.edu> wrote:
> >
> > Building from the latest sources on endeavouros (Arch):
> (snip)
> > Test ../../../src/zsh-2021-03-31/Test/Y01completion.ztst failed: output
> differs from expected as shown above for:
> > comptest $': *\t\t\t\t\t\t\t'
> > Was testing: _expand shows file types
>
> Same in Ubuntu, Fedora and macOS.
>
> It seems we need to call complete-word instead of expand-or-complete,
> and include _expand in the 'completer' style.
>
> The patch below works (all the test pass with the patch), but
> I'm not sure this is the best solution.
>
> In the patch I simply replaced expand-or-complete by complete-word
> in the function expand-or-complete-with-report() defined in comptest.
> (Do we also need to change the function name etc.?)
>
[-- Attachment #2: Type: text/html, Size: 1781 bytes --]
next prev parent reply other threads:[~2021-04-03 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 13:40 Vin Shelton
2021-04-01 4:05 ` Jun T
2021-04-03 11:32 ` Vin Shelton [this message]
2021-04-04 4:05 ` Jun. T
2021-04-04 14:00 ` Vin Shelton
2021-04-04 17:02 ` Daniel Shahaf
2021-04-05 14:58 ` Marlon Richert
2021-04-06 4:23 ` Jun T
2021-04-06 11:38 ` Marlon
2021-04-06 9:53 ` Oliver Kiddle
2021-04-04 18:27 ` Bart Schaefer
2021-04-05 0:39 ` Vin Shelton
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='CACeGjnVQamQM0r4d45CAHTOq=vERpQwiDUV0_SaKm_Ey_D+bPg@mail.gmail.com' \
--to=acs@alumni.princeton.edu \
--cc=takimoto-j@kba.biglobe.ne.jp \
--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).