From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 80c24546 for ; Wed, 14 Aug 2019 09:55:34 +0000 (UTC) Received: (qmail 26078 invoked by alias); 14 Aug 2019 09:55:29 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 44662 Received: (qmail 20266 invoked by uid 1010); 14 Aug 2019 09:55:29 -0000 X-Qmail-Scanner-Diagnostics: from mail-wr1-f48.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25538. spamassassin: 3.4.2. Clear:RC:0(209.85.221.48):SA:0(-2.0/5.0):. Processed in 4.371953 secs); 14 Aug 2019 09:55:29 -0000 X-Envelope-From: stephane.chazelas@gmail.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.221.48 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=HflS5Ws2RCBjQ+F9e1Enj1zurCwZHrLkrxBvc9i1B3Y=; b=ofafWv5l4mj/DxgejkAUlQod53pJEId+qhWOx5NMdMXyKQxUrrutbje/5hyV+hF7eX 5zGddNJQu0OF4IIrg0+YZi2n/ufJAWGTvNaLmA2PwFBU5beDPt96EAmd6c3ANtXIZyhX ROHbvToW1IhzQDJMN2G5DQq0VJsuFscHWggZT/YstF3rFkn+WTtwDHwOoIqn7lAb6biq MBRpMwc4UyyQtSAvreLg5DI6oj53DFDUWIQbVZv165E3IVePCguh9+fTRDtyEYr3Xm3a 1299iNxt/GqfZNkVK5twa/zZYf1c9K5qsoTcALrxXUZAkqMmwk4ndNUodEhocstV/T8y kRXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=HflS5Ws2RCBjQ+F9e1Enj1zurCwZHrLkrxBvc9i1B3Y=; b=q1mFbkqCo+zEaBj4nacbYD7ks8NAfrnfNimEM8o8bEQW5cLK7GrDnQ+EYtfJ4S0ZQW 9soYVF/FJJ9I1VxOxUn7e7CTdlbWgaFmRT1DODITinuFE6tuxFcjpUDrSUWrsu8+G2L1 9/At/IoMDqj/4C0o3y+Yi58oDeA6C6ioHhlvGxkmBGPD9jM0gJdFWXQAhFRt6PVdKGK6 +LAspZaDn0UqUFqsNk9xkuVC58rcnYeLkQp22U00erMhMtjM5gdpivVO0nPpfUqEDHvM HT8FGGVWnpNgfTUIXd6kBcPRkfI0p02ujMxB9eC1EtYyH8wcOIBcLNckHNG0skL/SMo8 BF1A== X-Gm-Message-State: APjAAAVNdSqdu0/9VQUCown5QRHW3LXYshN2jSjFZUu1psri5uSKU64o v3F0bwI8zAhcsOtgS0DOoJ4= X-Google-Smtp-Source: APXvYqxtA7lRBTwoVynF8+714Vhw0Jf+VVPAsu9+M6elVQ+F2cYXZVIZgOTOiiN4GmbIATWUR+tlfA== X-Received: by 2002:adf:f206:: with SMTP id p6mr53646600wro.216.1565776491689; Wed, 14 Aug 2019 02:54:51 -0700 (PDT) Date: Wed, 14 Aug 2019 10:54:49 +0100 From: Stephane Chazelas To: Aryn Starr Cc: zsh-workers@zsh.org Subject: Re: [Feature Request] Adding option to support triple quotes Message-ID: <20190814095449.s7mgevyo5tdhfyby@chaz.gmail.com> Mail-Followup-To: Aryn Starr , zsh-workers@zsh.org References: <6EA30061-5610-4CCA-93FB-0A160E2002A3@icloud.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6EA30061-5610-4CCA-93FB-0A160E2002A3@icloud.com> User-Agent: NeoMutt/20171215 2019-08-13 10:36:53 +0430, Aryn Starr: > Adding an option to zsh to support triple quotes > (TRIPLE_QUOTES) would make possible much more readable code. [...] We could also implement mksh's "$(<<'EOF' arbitrary text that mustn't end in empty lines EOF )" That already works in zsh, but is not optimised like in mksh as it does "$(cat <<'EOF' arbitrary text that mustn't end in empty lines EOF )" while mksh treats it specially as effectively a kind of quotes. mksh also supports $(<<'EOF' foo EOF) (though that's probably not POSIX). See also perl's q(...) and qq(...) that are more compatible with the shell syntax than those python '''/""". See: $ a="'"; print -r ${(qq)a} ''\''' -- Stephane