From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 40d39280 for ; Tue, 14 Jan 2020 18:35:10 +0000 (UTC) Received: (qmail 11085 invoked by alias); 14 Jan 2020 18:35:04 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 24664 Received: (qmail 9529 invoked by uid 1010); 14 Jan 2020 18:35:04 -0000 X-Qmail-Scanner-Diagnostics: from mail-lj1-f169.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25691. spamassassin: 3.4.2. Clear:RC:0(209.85.208.169):SA:0(-1.9/5.0):. Processed in 4.601976 secs); 14 Jan 2020 18:35:04 -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.208.169 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=UbV0wWqQx3wj3ZhsKdK/WiUzVe70th40J+ach+XTGRs=; b=ov1D76GfN0xOQuY+LNCbxrHkHd+Gl735nJSR3p2s+lLHYpQ/1rZ3Ev+T38l636Khco NPTuYZ88lP2gTEMgaQiNEMCZ8pIJX9Y6g8qmv4Q+NktEsvKPbOE3+cMktEmBJlJpi/IY TCU30PY48VUhjXiaA8zWoXvuaKG97k9jChVSTNuZdbL+os1F8mf1CLh0Fv2akCpgQSOQ UJkJ1wuyQ2Hq2YESPbxgclsrs7ekBJ+SDgMiddEKM6Sax8iraOPxKcnf0rWhHrUHPC9E +ri5uLTCnwxE1E309tfhimHplR5BA35kNODOWPzDaSZoJJaQ/mTQzKxiCTlaIZ+a8crN MK6w== X-Gm-Message-State: APjAAAUF7Ca9H/sLnlnd3AIsMxJ3E5ZIobP9K7SrTNgVjRe+gM3JUcFI xq7DdvUPPkAwWKF+AK8Tcamp6rsK495d6Ed4sbJbjg== X-Google-Smtp-Source: APXvYqyCPjLgyn7MK3hprYi2sF0nAQfNlaY1g+1whcXnKbQkEAAeB4n6ZeKM8P/DjIyioJM8Pu0tbITFIgBwU42tiyA= X-Received: by 2002:a2e:924d:: with SMTP id v13mr12936288ljg.267.1579026864813; Tue, 14 Jan 2020 10:34:24 -0800 (PST) MIME-Version: 1.0 References: <20200113170630.GA8134@tarpaulin.shahaf.local2> <1d1c62f2-7d74-4b6c-a08e-78dfe7378fc6@www.fastmail.com> <1579025111.4404.61.camel@samsung.com> In-Reply-To: <1579025111.4404.61.camel@samsung.com> From: Bart Schaefer Date: Tue, 14 Jan 2020 10:34:13 -0800 Message-ID: Subject: Re: problem with context specification To: Peter Stephenson Cc: Zsh Users Content-Type: text/plain; charset="UTF-8" On Tue, Jan 14, 2020 at 10:06 AM Peter Stephenson wrote: > > On Tue, 2020-01-14 at 16:45 +0000, Daniel Shahaf wrote: > > > I assume the stars are for matching every possible value for that segment, > > No. An asterisk matches zero or more characters, _including colons_. > > This can certainly be a right pain. It's important to remember that the colons are strictly a completion system convention -- they have nothing to do with the semantics of zstyle itself, which can use any sort of context patterns and style names. That's why completion styles explicitly begin with the fixed string ":completion:". I even spent a while experimenting with using it to construct an object hierarchy for a message-passing programming style (too slow to be more than a curiosity).