From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23385 invoked by alias); 27 Dec 2016 19:09:53 -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: 22290 Received: (qmail 10824 invoked from network); 27 Dec 2016 19:09:53 -0000 X-Qmail-Scanner-Diagnostics: from mail-ua0-f176.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.217.176):SA:0(-1.1/5.0):. Processed in 0.852829 secs); 27 Dec 2016 19:09:53 -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=-1.1 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,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.217.176 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=+xDIRYtx+JwxbEvVf2QlO4akshcecKcCXegka2w3hgw=; b=XpTjlI9j8g4DpPEm56X5U5ck6nySDtpsoeDE1oKySTxfXAj2jngCsYdI3oFqranO8e 2le5T/wLkkWqbFmRVP+ziVL4MtXu6Wv2mJ9uMImxlWRuUPIwnwibpEIxqt5qk264Ie+U sxjY/P8nll/i1MiEauLZVYUIet3dgP1BpfEensb/Drnf6XRNU9NBp8o1SMIFEnx5SUm/ 3RxOtPDLxHMXbId1CzS9NgHQJxAgL8PkazQlJ0SthSKwVv4AP2F3hu7JlVEGfsh0gXtO mNw9INscV26DjFJsaqZcjtXE3gS1+FpsaUbFViHoQyV03OYtaBATzsnkxyeefGAVT+wE kWSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=+xDIRYtx+JwxbEvVf2QlO4akshcecKcCXegka2w3hgw=; b=b7KAtF+Aqp/aCYKyIELYxrRe0GyXvbLh1VEYeGGbWHRTQEEwv+Hi4WB/BhjQKgU+eD 29Lj040rTT7a/nU6cjnjxoWK/XtQzpMsP535Sxnrtv/kQCeTlnaqn7rLFpRZiXu6jZUU y3ACiJ5nMMVGPuiE4CGJ19ers8vMG2FaSJsYuHGAak/barWIKANN66n6Tzwj9SmSaRIn 51G8BAl5YKFVVMQaNfm7wIp9cPqd6OiFkZN9mTR0zD2kz7yfEnhMs4tdge6+FGfgPqo0 LIapA5evGYTcz5YYwOqHqAUntBsnxtyg21g5zGvN3M0JsinwC74LQY4z86h06dXoRGuw sQUw== X-Gm-Message-State: AIkVDXLXA1EiHjMvyyhdeikTLHGRnjb7/HoruY/i8srrsdZpBcaIz7Sm646JjV8pgNpLCQ== X-Received: by 10.176.1.3 with SMTP id 3mr25132000uak.170.1482865785854; Tue, 27 Dec 2016 11:09:45 -0800 (PST) From: Bart Schaefer Message-Id: <161227110954.ZM1153@torch.brasslantern.com> Date: Tue, 27 Dec 2016 11:09:54 -0800 In-Reply-To: <99549001-5744-c36f-a4dc-404071aba08a@eastlink.ca> Comments: In reply to Ray Andrews "Re: append to history entry?" (Dec 27, 10:23am) References: <5288b537-f06a-d18a-60ea-1f962856c80c__41345.3811700039$1482803962$gmane$org@eastlink.ca> <20161227125530.GA4796@fujitsu.shahaf.local2> <161227080022.ZM519@torch.brasslantern.com> <99549001-5744-c36f-a4dc-404071aba08a@eastlink.ca> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Ray Andrews , zsh-users@zsh.org Subject: Re: append to history entry? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Dec 27, 10:23am, Ray Andrews wrote: } } Seriously, I wish I knew if stuff like that really is part of the best } of all possible worlds or if it is a case of fundamental errors in } design of the first shells Neither, really. It's a case of gradually accumulating requirements on what shells do, rather than any flaw in the original design. In the original design you'd have relied on external programs for all of this stuff. } Can't we have "print --Just-Do-It" ? That's what the -r option is, but print doesn't control how its arguments are processed as part of the command line parse, which is necessary for what you asked about. Seriously, you can't ask for a way to muck with something that is normally handled transparently by the shell internals and then gripe about having to replicate some of that hidden processing. Well, you can, but it doesn't really help. :-) Daniel is rather dogmatic about handling edge cases that I tend to ignore for the sake of not throwing out all the details that make you "take it on faith" (a phrase that makes ME grind my teeth whenever you write it). } One thing tho Bart, it seems it should be 'echo' because when the } command line is recalled and executed, the colon throws an error It shouldn't. There's no difference between "echo" and ":" except that ":" discards its arguments without printing them. If you're getting an error on ":" you've done something else to cause it. What error?