zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: gi1242+zsh@gmail.com
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Updates to the Plugin Standard
Date: Fri, 25 Oct 2019 23:39:24 +0200	[thread overview]
Message-ID: <CAKc7PVC3MVVmtj4S_4-HWEFnZCbd3DWL5WwYNUSqRXbzcKMrOg@mail.gmail.com> (raw)
In-Reply-To: <20191025190645.GN18530@andrew.cmu.edu>

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

pt., 25 paź 2019, 21:08 użytkownik <gi1242+zsh@gmail.com> napisał:

> 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 – available) but
otherwise problematic ASCII character '/' has been selected to them. The
other available characters, like ^ aren't available because of the <= 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 :<TAB> 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 …-prefix in one of my projects 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: …zp-test-make-targets.

GI
>
> --
> 'Common' Proof Techniques:
> 12. Proof by obfuscation -- A long plotless sequence of true and/or
> meaningless syntactically related statements.
>

>

      reply	other threads:[~2019-10-25 21:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 18:21 Sebastian Gniazdowski
2019-10-25 18:53 ` René Wilhelm
2019-10-25 19:06 ` gi1242+zsh
2019-10-25 21:39   ` Sebastian Gniazdowski [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=CAKc7PVC3MVVmtj4S_4-HWEFnZCbd3DWL5WwYNUSqRXbzcKMrOg@mail.gmail.com \
    --to=sgniazdowski@gmail.com \
    --cc=gi1242+zsh@gmail.com \
    --cc=zsh-users@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).