zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: "the backslashes" Re: Dynamic directory name function
Date: Thu, 24 Sep 2015 09:50:19 -0700	[thread overview]
Message-ID: <150924095019.ZM1066@torch.brasslantern.com> (raw)
In-Reply-To: <20150924171031.3ed2bc9c@pwslap01u.europe.root.pri>

On Sep 24,  5:10pm, Peter Stephenson wrote:
}
} >     zstyle ZDN_wrapper_name zdn_top=(
} > 	g   ~/git
} > 	ga  ~/alternate/git
} > 	gs  /scratch/$USER/git/:second2
} > 	:default: /:second1
} >     )
} 
} That can be made vaild syntax by a bit (?lot?) of trickery with reserved
} words, but what does it mean, and what gets passed to the command?

It means exactly the same thing that writing it now without the equal
sign and parens means; it's merely syntactic sugar so you don't have
to use backslash-continuation to spread it across multiple lines.

Whether it gets exploded out into an ordinary argv before being passed
to bin_zstyle, or comes in as some other structure that bin_zstyle
itself unpacks, is an implementation detail for module, I'd expect.

No matter, was just a thought I threw out.


  reply	other threads:[~2015-09-24 16:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150922204251.05f3d291@ntlworld.com>
     [not found] ` <150922210756.ZM30253@torch.brasslantern.com>
     [not found]   ` <20150923094821.5c5d0b80@pwslap01u.europe.root.pri>
     [not found]     ` <150923231024.ZM32382@torch.brasslantern.com>
     [not found]       ` <20150924093752.581dcee9@pwslap01u.europe.root.pri>
2015-09-24 15:10         ` Bart Schaefer
2015-09-24 15:18           ` Peter Stephenson
2015-09-24 15:34             ` Bart Schaefer
2015-09-24 16:10               ` Peter Stephenson
2015-09-24 16:50                 ` Bart Schaefer [this message]
2015-09-25 13:13         ` Peter Stephenson

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=150924095019.ZM1066@torch.brasslantern.com \
    --to=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).