From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22131 invoked by alias); 3 Dec 2015 23:44:01 -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: X-Seq: 37299 Received: (qmail 23467 invoked from network); 3 Dec 2015 23:44:01 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=FQsKUhf1MiMEQ0d5ZWo3l+uUgpc=; b=uvVqvm /n9iKcbJr3JozUtrdqpaVmXsPAsj4YfpeASi00/XZHahfBnzk7lR48Vi97GW2isq hsRpmtTeXk92zIU5jLjildp2w9SxE02y2/A/daKoLVB3DzL/PR7QkTkhYCdp80YX by3nJmolUNGCMJ/bAo1UDR7f7k3TZLQYyGTXs= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=FQsKUhf1MiMEQ0d5ZWo3l+uUgpc=; b=CkOye IzG40IotrkB/AUiAS4Ky6rb+I2HyRS0GFLA5uyhXsUTkqBBIMa/TJMvSe4kM5/Fg N6WJv0MH1oiHcP0+R/13inmQSbKXHRIoJScQLA5F2N3n6AMGTug33Xc3yb9tZLT7 SQJz4VFVB2Eh+2jaRc1T19rWra9QxSqzlULuEg= X-Sasl-enc: qLSF9+S0m9IsavDVFCgj5DrMdy+TAR7wv/x68/Kz9XjQ 1449186239 Date: Thu, 3 Dec 2015 23:43:57 +0000 From: Daniel Shahaf To: Vincent Lefevre Cc: zsh-workers@zsh.org Subject: Re: The "set" utility outputs binary data Message-ID: <20151203234357.GG1955@tarsus.local2> References: <20151203140558.GA17469@zira.vinc17.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151203140558.GA17469@zira.vinc17.org> User-Agent: Mutt/1.5.21 (2010-09-15) Vincent Lefevre wrote on Thu, Dec 03, 2015 at 15:05:58 +0100: > The "set" utility outputs binary data (probably due to escape > sequences for coloring and so on in some parameters such as > prompts): ... > This is also important when the output is on a terminal. History expansions have a similar issue: after running . bindkey ^T f (where ^T is a control character, inputted as ^V^T) . and then issueing a history expansion !! the ^T is rendered, not as the two characters "^" "T" in reverse video, but as a literal ^T, which my terminal renders as a box with "0 0 1 6" inside it (the codepoint). Printing an easier-to-read representation would be nice, although of course it's a minor issue.