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=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,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 c2849ba0 for ; Fri, 25 Oct 2019 21:40:23 +0000 (UTC) Received: (qmail 14771 invoked by alias); 25 Oct 2019 21:40:13 -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: 24387 Received: (qmail 5654 invoked by uid 1010); 25 Oct 2019 21:40:13 -0000 X-Qmail-Scanner-Diagnostics: from mail-vk1-f177.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.0/25608. spamassassin: 3.4.2. Clear:RC:0(209.85.221.177):SA:0(-1.0/5.0):. Processed in 3.655276 secs); 25 Oct 2019 21:40:13 -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.221.177 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pIw+O7u6TY9bvFwP08jj+wg2m5S6ZE+dOWUIPyds6Uk=; b=giaGDVSFTT1X2niRJA6c2+7ZLWvp/z2tyFqqgcWkZ881a0k8BPyIRZWt+5ZFRwKQr5 oquMciPX0geTYuXbdF5HSnL6MlQfUGPaR3qFwXOicjRJ3Iqkv2wsmNJBlR4K4OUQeHxg F7Wq6oXX8OkmK0SV6oAjjwRZ+oOaNZir+hMpvQFqFFXtWyiPDUHUidKLl3jduCztxXHr X0Zac+gP6cWo70xULiRlYHscmh4frhEpt4h6X+HxE8uz5Q6Dj3n3RcPufOXOUqQDKcPM +EqlymmmK7K6lJKsd3wlMCgCkeNgyLWNOlEakMwPc6cfmkvjwXAN3Pcy2KVBpT1FtqXl ekKA== 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=pIw+O7u6TY9bvFwP08jj+wg2m5S6ZE+dOWUIPyds6Uk=; b=H5bqpr3wIpsVCFPiFXXmF5LN6x/z/eftn5C0dOttcXV3JxRBenhUEc77NKUntmoZaq j7pe7FSZ37Bsp3iDuc4tWBstlxVu5RHCcA3BEuwC0ULkLJdfqsA5sLeRKl3RrdeYl4NI PlYUO3+x6etbyDT/tPNXTxEP9TyWJsdw4JANTAIEjwZ/xhJsqCwdAvj41rvijUD/m5Qw sOiKNSAoSgLk56e2rws+gNfiVj82ABPeqEzwDNOf1iDl36QaC7t4nng0JsbK6fVFc1xp wgZqifd8GvO4T4jLDV4/u9NIxg9cv6DYpyD+v8wjdIY/lvgKaHswt1k6GuA2V5HM9lJ5 KJfw== X-Gm-Message-State: APjAAAXbDa0DiEJF2DGgMhOMoRUBC/vIaFrggXZTeH8Hb1r3LYRpcwWc WJ16gGn4CyakKoXaLpYRRtYQK/JohiYDB61rGN4= X-Google-Smtp-Source: APXvYqwiwXgtEd9AcJUjPhGl2qCu6mOHrX9keEYzPmi3+7uBKlojLln6+431fZMsWwbvBhAqXVDg2za7BRvHClEB1a4= X-Received: by 2002:ac5:cb62:: with SMTP id l2mr3335530vkn.32.1572039576014; Fri, 25 Oct 2019 14:39:36 -0700 (PDT) MIME-Version: 1.0 References: <20191025190645.GN18530@andrew.cmu.edu> In-Reply-To: <20191025190645.GN18530@andrew.cmu.edu> From: Sebastian Gniazdowski Date: Fri, 25 Oct 2019 23:39:24 +0200 Message-ID: Subject: Re: Updates to the Plugin Standard To: gi1242+zsh@gmail.com Cc: Zsh Users Content-Type: multipart/alternative; boundary="0000000000008052ec0595c2fcbd" --0000000000008052ec0595c2fcbd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable pt., 25 pa=C5=BA 2019, 21:08 u=C5=BCytkownik napisa= =C5=82: > I took a quick look at the namespace prefix section: That looks a bit > overkill to me. Also using . and / as function prefixes can easily get > confused with paths. > > I'd suggest using just one name space prefix for everything to keep > things simple. It could be ::function, or pluginName::funciton for > instance. > The section has purely advisory character. However for the pluginName:: proposal there's a valid argument - the possible conflict as in https://github.com/zdharma/fast-syntax-highlighting/issues/157. As for the points about the dot and / prefixes, I'll take them into consideration. Right now I can tell that the / prefix is used for debug functions because they're most outside from the main code. They're side to the main code, hence the overall nice (and most of all =E2=80=93 available)= but otherwise problematic ASCII character '/' has been selected to them. The other available characters, like ^ aren't available because of the <=3D 5.7= .1 autoload bug (https://www.zsh.org/mla/workers/2019/msg00534.html) however hence / isn't available for autoload anyway, the character might get changed. Any propositions for a replacement? If there are too many types, it makes it more confusing / cumbersome > when writing. > My subjective impression is that the : prefix is especially useful. Many functions are hooks, and it's nice to list them as in https://asciinema.org/a/277059, just to see them grouped (noticing: they're cannot be directly completed, entering : tries to complete the modifiers, is there a way to change this?). I foresee that the number of prefixes will not get smaller, it might get, however, larger, when the Unicode characters will get mentally accepted into consideration. I'm already using =E2=80=A6-prefix in one of my project= s as it's easy to type (Alt-k on my keymap), to denote a "backend function", i.e. a function that is a closed black-box -like thing that is getting the requests to do the dirty work at the end of a multi-stage preparement. The function is called: =E2=80=A6zp-test-make-targets. GI > > -- > 'Common' Proof Techniques: > 12. Proof by obfuscation -- A long plotless sequence of true and/or > meaningless syntactically related statements. > > --0000000000008052ec0595c2fcbd--