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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI 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 cdb4d175 for ; Wed, 24 Jul 2019 14:19:36 +0000 (UTC) Received: (qmail 26788 invoked by alias); 24 Jul 2019 14:19:28 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 44572 Received: (qmail 17750 invoked by uid 1010); 24 Jul 2019 14:19:28 -0000 X-Qmail-Scanner-Diagnostics: from mail-vs1-f52.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25517. spamassassin: 3.4.2. Clear:RC:0(209.85.217.52):SA:0(-2.0/5.0):. Processed in 2.445158 secs); 24 Jul 2019 14:19:28 -0000 X-Envelope-From: sgniazdowski@gmail.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.217.52 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=0sioaAVfI3cqiSYBLHIrIdi0XouGoY3N8pBzIxAaLko=; b=aLvPJY2oZGcBrYKYYmQYRYIME5iEbo4r9tpuyhVTHX/MhySP3D5A2r+8uaWZhr+IbZ VHYu8Z1WO1S9kE9s5CYRB86Um4QrETP+a8RNK1fxW83fmAuERJEJgZaU+384+D8AxS5h AxlbDlkuWtmqWT8hAaKrO/HpROC+cYiQ/JNn2QjFg84DpybxZw9HHI90XivQ3byaxb9i mcq50pn1Wgm8vNz3iD07hAS69u+rVp7yOWfvW3Yp45eLTzmjIEIp2EUMK8NjwW2WW5sZ xvGAm3Yok6aXE8a/m1n0p6AC+4l2V5//IoKNvT7gwmvUOznYch/FQ5MyZQ64VB1X9xQg qyJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0sioaAVfI3cqiSYBLHIrIdi0XouGoY3N8pBzIxAaLko=; b=QRGenZF8NyCxqsc7nfvKvzEEvQeQwIyxbkqMUNqvrzTLRBVbNiKWHIBmHSbo6V7cJ7 WLPd83pWRMTwFfl4WZZ1Q7h/5qXdacwfqDuzmd7MZKG86p95UgHxe1TbioApzCDJLD0N Q/46JqFYFvCKJdlNLbTVvmlICv92ydg0TLxqZhhAr71z13TcOTm1+PnWD6bce8W17Pvd uEu5zkTfZzIY05ytJ80J4jcWACl9CQzk7W0yA/9WCHCFL5IGXSh1wHD2oLd8s4/yioa5 9F+dalslb2KVkLUZOm+BYs3WvZSlDcqY/tQoWCQ7561qFxkZlecXb9lYzURU1iswHOkB dIOw== X-Gm-Message-State: APjAAAWIPAo1KnR4caWyI19tgzoPiolHrKRNGLlE3tsX8B0CaDChve9W /dwg7yxrBFuWyXTo0p+WKXiy9WNcvhyqtqJEOj0yXBCE X-Google-Smtp-Source: APXvYqwuDMAMRuFywGtd1I28+/Hd1rs6hsfPp2WXkA9zRFhqlfQylRZkBIKWUp+TxLGz2sPr8fWibylnt6ZBUzM+TXk= X-Received: by 2002:a67:80c8:: with SMTP id b191mr53377079vsd.113.1563977932755; Wed, 24 Jul 2019 07:18:52 -0700 (PDT) MIME-Version: 1.0 From: Sebastian Gniazdowski Date: Wed, 24 Jul 2019 16:18:41 +0200 Message-ID: Subject: How to disable completion for a builtin? (actually a reserved word) + an apparent bug To: Zsh hackers list Content-Type: text/plain; charset="UTF-8" Hello, I would like to disable the completion for the declare builtin. How to accomplish this? A side-note: disabling declare doesn't help. Also, it's actually impossible to disable the command (it will still work), probably because it's a reserved-word, not (only) a builtin. I wonder, couldn't the disable effect be emulated in this case? Because from user's point of view, declare is a typical builtin so disable should work, what is also suggested by the disable command returning no errors. -- Sebastian Gniazdowski News: https://twitter.com/ZdharmaI IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin Blog: http://zdharma.org