zsh-users
 help / color / mirror / code / Atom feed
From: Marc Chantreux <eiro@phear.org>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: zsh at perl conference and few questions
Date: Sat, 28 Apr 2018 12:14:02 +0200	[thread overview]
Message-ID: <20180428101402.GA16083@prometheus.u-strasbg.fr> (raw)
In-Reply-To: <20180423110642.0e0a5ebe@camnpupstephen.cam.scsc.local>

hello,

thanks for your reply

> It's quite hard to ensure alternative syntax gets parsed consistently
> --- I'm sure there are lots of inconsistencies --- but a lot of that is
> hidden.

well... i used it at least 15 years long without having problems so
we can imagine it's consistent enought :)

> > b) why the while loop can't take (( )) or single instruction as do
> > list ?
> 
> Maybe because it's missing the code at the bottom?

should this code be merged in the zsh codebase ? :)

> > c) it seems the (+) syntax can't be used outside file expansions
> >    (or did i miss something?)
> 
> Yes, there's no general "execute a function that does something" in
> other cases because there's no obvious definition of whit it would do
> --- unlike globbing qualifiers which are there as a simple filter.

is it a possible open discussion with zsh-workers ? it seems to me i
have a clear idea of how things could work but i have now idea of how to
implement it. maybe i should document it ? (or maybe there are some
archives outthere about why it cannot be obvious?)

> > d) is there a plan to have something like namespaces ?
> It was first discussed a long time ago, but no one has bitten the
> bullet.  Simple minded namespaces --- allow dots in the variable works
> --- are trivial, but the variable code is very complicated and working
> out how to do it properly is a big task that no one has been prepared to
> look at (saying "someone else ought to do this" does not count as
> looking at it" :-)).

in this case i wasn't talking about variables but only function names but
i imagine it goes the same.

once again thanks for your reply.

regards
marc


  reply	other threads:[~2018-04-28 10:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180423093610epcas4p2248cf6f0e76bd3e81ff6fa0ef55f5c25@epcas4p2.samsung.com>
2018-04-23  9:24 ` Marc Chantreux
2018-04-23 10:06   ` Peter Stephenson
2018-04-28 10:14     ` Marc Chantreux [this message]
2018-04-30  3:30     ` Sebastian Gniazdowski
2018-04-30 12:52       ` Marc Chantreux
2018-04-30  5:28     ` Bart Schaefer
2018-04-30 12:57       ` Marc Chantreux
2018-04-30  3:06   ` 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=20180428101402.GA16083@prometheus.u-strasbg.fr \
    --to=eiro@phear.org \
    --cc=p.stephenson@samsung.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).