zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Support the mksh's ${|func;} substitution
Date: Fri, 13 Sep 2019 22:28:09 +0200	[thread overview]
Message-ID: <CAKc7PVD8yXmFrafUy+qZXThM60E6OCz4OJ7u9+PGUB-fdycrkA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bqTStbE9DSMVaTc940GEucNhpZ6oXs+4c__TK+nCR-wA@mail.gmail.com>

Ok, thanks for the clarification. I've gathered the information in a
markdown document:

https://github.com/psprint/zsh/blob/master/x-flag.md

It seems fairly complete, now only someone who knows how to evaluate
code would have to implement it or provide hints, as my tries with
using bin_eval (the eval function that's behind it is declared static)
didn't result in a working ${|...;} substitution.

On Thu, 12 Sep 2019 at 08:55, Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Wed, Sep 11, 2019 at 11:01 PM Sebastian Gniazdowski
> <sgniazdowski@gmail.com> wrote:
> >
> > On Thu, 12 Sep 2019 at 07:35, Bart Schaefer <schaefer@brasslantern.com> wrote:
> > >
> > > $REPLY means nothing after the code has run -- it's strictly an input.
> > > $reply is the only output.
> >
> > Yes I was opting for such settlement, however what you wrote seems
> > contradict to:
> >
> > > 4. else if REPLY is set, the value of REPLY is used
> > >    (so the corresponding element changes, possibly to an empty string)
>
> Yes, I was imprecise/absentminded in the former paragraph ... that
> first sentence should have said:  REPLY means nothing if reply is set
> after the code has run.
>
> As the examples demonstrated, the latter paragraph numbered 4 is the
> correct interpretation.



-- 
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org

  reply	other threads:[~2019-09-13 20:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06  0:52 Sebastian Gniazdowski
2019-09-06  0:54 ` Sebastian Gniazdowski
2019-09-06 23:16 ` Sebastian Gniazdowski
2019-09-07 12:16   ` Daniel Shahaf
2019-09-07 15:07 ` Stephane Chazelas
2019-09-07 18:09   ` Sebastian Gniazdowski
2019-09-07 20:19     ` Stephane Chazelas
2019-09-07 21:19       ` Sebastian Gniazdowski
2019-09-10  2:20         ` Sebastian Gniazdowski
2019-09-10  5:29           ` Bart Schaefer
2019-09-10 18:21             ` Sebastian Gniazdowski
2019-09-10 19:38               ` Bart Schaefer
2019-09-12  0:08                 ` Sebastian Gniazdowski
2019-09-12  1:03                   ` Bart Schaefer
2019-09-12  2:06                     ` Sebastian Gniazdowski
2019-09-12  5:35                       ` Bart Schaefer
2019-09-12  6:00                         ` Sebastian Gniazdowski
2019-09-12  6:55                           ` Bart Schaefer
2019-09-13 20:28                             ` Sebastian Gniazdowski [this message]
2019-09-13 21:33                               ` Bart Schaefer
2019-09-13 21:36                                 ` Bart Schaefer
2019-09-14  0:41                                   ` Sebastian Gniazdowski
2019-09-14  0:44                                     ` Sebastian Gniazdowski
2023-05-03 14:46 Sebastian Gniazdowski
2023-07-04  1:55 ` Bart Schaefer
2023-07-04 18:53   ` Lawrence Velázquez
2023-07-05  5:32     ` Bart Schaefer
2023-07-05  6:30       ` Bart Schaefer
2023-07-06  1:39       ` Bart Schaefer
2023-07-06  2:27         ` Mikael Magnusson
2023-07-06  4:00           ` Bart Schaefer
2023-07-18  3:14             ` Bart Schaefer

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=CAKc7PVD8yXmFrafUy+qZXThM60E6OCz4OJ7u9+PGUB-fdycrkA@mail.gmail.com \
    --to=sgniazdowski@gmail.com \
    --cc=schaefer@brasslantern.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).