zsh-workers
 help / color / mirror / code / Atom feed
From: Marlon Richert <marlon.richert@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Don't complete dirs as suffix aliases
Date: Mon, 30 May 2022 14:51:12 +0300	[thread overview]
Message-ID: <CAHLkEDsrBFhAFV6Csf4y_QqN_Kh_MXf9z9X=n5+4XYB5zowDaw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7br7e8qhV4um-PTdCk2uih8EPZMUGzDDBBd5qsnU0+o-g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 210 bytes --]

On Thu, May 12, 2022 at 8:44 AM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> What's the .vscode/settings.json file in the patch?

Oh, whoops, that shouldn't be there. Here's a new version of the patch.

[-- Attachment #2: 0001-Don-t-complete-dirs-as-suffix-aliases.txt --]
[-- Type: text/plain, Size: 718 bytes --]

From 43c3a62e747b50c3b7454902f737d4e6bbdc2845 Mon Sep 17 00:00:00 2001
From: Marlon Richert <marlonrichert@users.noreply.github.com>
Date: Wed, 11 May 2022 10:18:16 +0300
Subject: [PATCH] Don't complete dirs as suffix aliases

---
 Completion/Zsh/Type/_suffix_alias_files | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Completion/Zsh/Type/_suffix_alias_files b/Completion/Zsh/Type/_suffix_alias_files
index 1c2c8ebb5..de3e2b9d9 100644
--- a/Completion/Zsh/Type/_suffix_alias_files
+++ b/Completion/Zsh/Type/_suffix_alias_files
@@ -16,6 +16,7 @@ else
     tmpa=(${(kq)saliases})
     pat="*.(${(kj.|.)tmpa})"
 fi
+pat+='(#q^/)'
 
 # _wanted is called for us by _command_names
 _path_files "$@" -g $pat
-- 
2.36.1


      reply	other threads:[~2022-05-30 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  7:37 Marlon Richert
2022-05-11  8:03 ` Mikael Magnusson
2022-05-11 10:44   ` Marlon Richert
2022-05-11 11:18     ` Peter Stephenson
2022-05-12  5:44 ` Bart Schaefer
2022-05-30 11:51   ` Marlon Richert [this message]

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='CAHLkEDsrBFhAFV6Csf4y_QqN_Kh_MXf9z9X=n5+4XYB5zowDaw@mail.gmail.com' \
    --to=marlon.richert@gmail.com \
    --cc=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).