From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26288 invoked by alias); 9 Nov 2016 22:10:38 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22106 Received: (qmail 25678 invoked from network); 9 Nov 2016 22:10:38 -0000 X-Qmail-Scanner-Diagnostics: from mail-qt0-f181.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.216.181):SA:0(0.0/5.0):. Processed in 0.71377 secs); 09 Nov 2016 22:10:38 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.216.181 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=O7LzQOlpCMxvk1uXG4U0WX1em4/quFDtqRLOZbJaFEY=; b=c+EEuC+OUMRjyhCscVXgGXA0NY3BysEqF2YgGTSmez9BFH/VnxyO/CG8ApQC7IATQT SD0IWPwGzsYxfJRo1O243+3CZt5gTS+9dRNpW8Gnm2Ng+J7odm+pPRRdWYmjAZxpiRNi cVNdSLKFZSntC7MWHqYG6FHXHvqUc6WsQKg3XhgombIpt4M7c9MIQpSbUspvXtCsMEBK fMWHz8pKsnGYJwMjEKvWAOG/ss69dVKcFhKEyr/w35WQC/pIEMA9PoD8HderS5gNe7MN 9CKnAi4zQ+RTXsApdQzIyD2rucvTw61+1ylQajNIkR6AbHFRDT76gIFEAUUqKxuGwhR4 XUWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=O7LzQOlpCMxvk1uXG4U0WX1em4/quFDtqRLOZbJaFEY=; b=UCMhWOikEEMUVMJ+cPfy2Hzf0huZ0GmF+c73rmTeqxPYjXeZgVSG66FxtTtmzHT0EV M8linCCnJwFXyVon4IYVDfI1MvlpW74CGhNi6i2LxvL+IqCucOcSor0yrnV7ASX3hMRE xZoqH7iyglhWpnAVq6ER2+SKO2fHnX27l1XFXyPaAfFkB1/1B/jevkB4nw5cmM/K6vN/ OdjCUBja6DMtwScoyR+ZZLk8NNtKh6v/x24DON79Mzy+6jdjQPigEmsmtIa6+gDXyJiT /W8S5LwqsQ6e956wntmqpBQE0OUDzlRyTlFguZV5CjiZlYCTMRDpwlRZQJwp153BI14C iPag== X-Gm-Message-State: ABUngven6zMvPufJiKNMHl4n11QlpeITkVDSIG08Hb9shQ+f9Zn0Ft8sbefcDbx0W33FWV+VTKiU7FyLgMSLKA== X-Received: by 10.200.42.232 with SMTP id c37mr1485392qta.145.1478719661616; Wed, 09 Nov 2016 11:27:41 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20161109180219.GA28703@aurora-borealis.phear.org> References: <20161109180219.GA28703@aurora-borealis.phear.org> From: Bart Schaefer Date: Wed, 9 Nov 2016 11:27:41 -0800 Message-ID: Subject: Re: would it be nice to support =<< ? (not the haskell one) To: Zsh Users Cc: Marc Chantreux Content-Type: text/plain; charset=UTF-8 On Wed, Nov 9, 2016 at 10:02 AM, wrote: > > i was thinking of a =<< operator so we could write > > element=<<. > { "user": "$USER", "uid": "$UID" } > . You can do this: element=$(<<. { "user": "$USER", "uid": "$UID" } . ) This is handled efficiently, with a minimum of forking. Note that it's necessary to follow the end marker with a newline before adding the closing paren.