zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: backward-kill-shell-word widget
Date: Wed, 13 Jan 2016 09:38:54 +0100	[thread overview]
Message-ID: <CAKc7PVB8=7Z5jU31Brpb1YW6MGZeB7e+VmpE038ZrOicn=bEVA@mail.gmail.com> (raw)
In-Reply-To: <20160113011850.GC2736@tarsus.local2>

On 13 January 2016 at 02:18, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> Sebastian Gniazdowski wrote on Mon, Jan 11, 2016 at 09:05:55 +0100:
>> for script (${location}/*\.plugin\.zsh(N)) -zgen-source "${script}"
>>
>> Noshortloops breaks zgen, and short loops are AFAIK harmful as they
>> limit Zsh's detection of syntax errors.
>
> I don't think this line of conversation is constructive.
>
> If you are aware of bugs in zgen or antigen, report those bugs to the
> respective projects.  But please don't spam -workers@ with mails that
> have no content other than enumeration of flaws in existing projects.

I saw this different, as an occasion to somewhat introduce Github
community to original Zsh mainstream. I think there's a crack between
that mainstream and the community, e.g. OMZ. Maybe I'm wrong as
zsh-syntax-highlighting was successfully introduced to Zsh-users on
Github.

All Github flavors of Zsh share one thing: fpath prepending "plugin
architecture". 115 plugins gathered on "awesome-zsh-plugins" Github
page. Guessing that almost all in spirit of colorful prompts,
completions, grepping, sedding. Not in spirit of patterns, zsh-lovers
or the book. That's a crack I think. I thought that I introduce how
the vital Github macrocosm operates (the "plugin architecture") so
that maybe there would arise a resolution to this. If Zsh mainstream
would design well thought through plugin architecture, then it would
be like this: rock solid architecture + any level of naivety (or
innocence:) of contributions (plugins). What should that
rs-architecture do? I leave this intentionally unsettled yet and
choose to occasionally test zgen, antigen or OMZ on myself, waiting
for ideas. But one thing that came up to me are reports from plugin
operation. If one could easily see a generated text document that
would enumerate which options, zstyles, aliases, etc. a plugin sets or
creates, then it would be possible to still own the system despite
dropping naive (or innocent:) plugins into it.

That said I accept OMZ, zgen, antigen despite they can be users stuck
in 'Zsh is about dropping parenthesis in variable assignment and about
[[ instead of [', mostly because their code just works (if
noshortloops isn't set ;), and users can just use the software (also,
fpath-based plugins are currently innovative). That's why I submitted
ZNT to OMZ and now await for merge of ZCA. I wonder if my email would
offend Robby Russell. I really shown acceptance by submitting my
projects to OMZ. But this doesn't change that we should care about
breaking out of the stuck to seeing that Zsh is about e.g. patterns,
not lack of parenthesis in assignment.

Best regards,
Sebastian Gniazdowski


  reply	other threads:[~2016-01-13  8:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01  0:37 Daniel Shahaf
2016-01-10  7:42 ` Sebastian Gniazdowski
2016-01-10  7:54   ` Sebastian Gniazdowski
2016-01-10 20:13   ` Daniel Shahaf
2016-01-10 13:37 ` Sebastian Gniazdowski
2016-01-10 19:59   ` Daniel Shahaf
2016-01-10 21:06     ` Bart Schaefer
2016-01-12  8:23   ` Bart Schaefer
2016-01-10 15:50 ` Sebastian Gniazdowski
2016-01-10 20:19   ` Daniel Shahaf
2016-01-11  8:05     ` Sebastian Gniazdowski
2016-01-12 10:36       ` Sebastian Gniazdowski
2016-01-13  1:18       ` Daniel Shahaf
2016-01-13  8:38         ` Sebastian Gniazdowski [this message]
2016-01-14  0:13           ` Daniel Shahaf
2016-01-14  6:54             ` Bart Schaefer
2016-01-15  6:26               ` Daniel Shahaf
2016-01-10 17:17 ` Bart Schaefer
2016-01-10 19:53   ` Daniel Shahaf
2016-01-12  7:54     ` Bart Schaefer
2016-04-14 16:21   ` Bart Schaefer
2016-07-08 14:19   ` Oliver Kiddle
2016-01-11 11:53 ` Sebastian Gniazdowski
2016-01-12  6:59   ` Bart Schaefer
2016-01-12  7:49     ` Sebastian Gniazdowski

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='CAKc7PVB8=7Z5jU31Brpb1YW6MGZeB7e+VmpE038ZrOicn=bEVA@mail.gmail.com' \
    --to=sgniazdowski@gmail.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).