From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 6579 invoked from network); 27 May 2020 03:33:20 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 27 May 2020 03:33:20 -0000 Received: (qmail 17341 invoked by alias); 27 May 2020 03:33:15 -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: 45927 Received: (qmail 2028 invoked by uid 1010); 27 May 2020 03:33:15 -0000 X-Qmail-Scanner-Diagnostics: from mail-ot1-f50.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25821. spamassassin: 3.4.4. Clear:RC:0(209.85.210.50):SA:0(-1.9/5.0):. Processed in 1.957246 secs); 27 May 2020 03:33:15 -0000 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.210.50 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=6QcxACsv0XmDFl1mFnxCFAUHuD8MCurjMCFYMlpdjEY=; b=nO/tZ5dvfZ62lFQxGtpmNsJgb1QVA8vvNkGPMEqpHeHhs0a2CQpxctHaNyJlQZczQ0 0d2JNyr2Cwd7TKgPcjTG2iMF6/mKyWDj7+cJECTHzeamY/DMaSQZtrzz/ockZpguec1T gh7tQMJjIGWymZs89v9XbIDN8mjZFZAlG5t7SbVuw773N/zwzd8xSD9UjuKLbzl3xHS3 NVzBCQNwKfdyGF0ACC8pWJg19ZrI4ki1czKn66h6ArTil6mZBxXX0CHNbOFNcpbSqAZo LvhQtSXwXmY4nQzH2ywtOmeFgiBXTKbtCmTULIMB9Vkqthlv433O22tiAr59QpyOfVuE LDag== X-Gm-Message-State: AOAM531lRYT/tLZGMR4pNwZhyQpQit71zH4iXQF9JYZ33tf/2w90btgn tSMKYaMI/NfLvXu/sNGFrAq7maxHzJZTACddj0C0G0knPVo= X-Google-Smtp-Source: ABdhPJwi+mny0/red6+3FDEYJ2mmGekSFsb8uqrajuq+6210MNFI+6L6x3by4MBLQA9MONvsm8sY6cxYuDKQjvgx05I= X-Received: by 2002:a9d:20e7:: with SMTP id x94mr3401862ota.260.1590550360064; Tue, 26 May 2020 20:32:40 -0700 (PDT) MIME-Version: 1.0 References: <20200523022807.08f3ba45@tarpaulin.shahaf.local2> <20200525023515.7855610a@tarpaulin.shahaf.local2> In-Reply-To: From: Bart Schaefer Date: Tue, 26 May 2020 20:32:29 -0700 Message-ID: Subject: Fwd: Editing the history in the shell To: Zsh hackers list Content-Type: text/plain; charset="UTF-8" On Sun, May 24, 2020 at 7:35 PM Daniel Shahaf wrote: > > Bart Schaefer wrote on Sat, 23 May 2020 14:30 -0700: > > @@ -133,6 +140,28 @@ if ((fun)) then > > + for (( hist=1; hist <= savehist; hist++ )) print -rs -- "$var[hist]" > > This generates a syntax error when SHORT_LOOPS is unset. I think zed has a long-standing problem with SH_WORD_SPLIT and probably some other SH_ options? % setopt shwordsplit % zed "/tmp/one two" Where does this go? % cat "/tmp/one two" cat: '/tmp/one two': No such file or directory % cat /tmp/one Where does this go? % So ... how far do we go to make "zed" compatible with nonstandard options, and how do we approach doing it? Try to use entirely portable syntax, or invoke "emulate -L", or something in between? Look at the handling of function names, too -- it creates the empty function definition with ${(q-)1} but makes no attempt to quote $1 when calling "functions" or "autoload".