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 31563304 for ; Fri, 28 Jun 2019 10:13:22 +0000 (UTC) Received: (qmail 10799 invoked by alias); 28 Jun 2019 10:13:17 -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: 44467 Received: (qmail 7522 invoked by uid 1010); 28 Jun 2019 10:13:17 -0000 X-Qmail-Scanner-Diagnostics: from mail-wm1-f45.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25489. spamassassin: 3.4.2. Clear:RC:0(209.85.128.45):SA:0(-2.0/5.0):. Processed in 2.068698 secs); 28 Jun 2019 10:13:17 -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.128.45 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=2WTGIgfPb8gHuOX0eUAFi/1Td8Fsoz17QczT+w+WBuY=; b=nM6Cph6ryE3o9+LuVaBdvBnajwJHyjZrE0f5CgnAUB6/P+YCsy2GdMsUeDVp5sRgy8 XQQtmWtjJ9fbAlSl+VO0ewV7RLs1iMEHzpWbPwx9vXQkipOPwTuyCZtDbONy/2Z32+WX Dhfpg39aox1gTjWocWBiQ98bXdyiDRQ/hmFW3CYKPPZ6O9txb2xMenAyiwyUJ4+m1beq kncfTGXFplvcRi3B5vG1fX4DuHXTHKvKxhVt4ES699xL+MnR2Ylt6joISX9yNHL8sx7x tK6CrDIcNyVV8B9FZIRnVnbMJ6Md729L4jsbLtddlux6d82ydhMtd9kazuBoQdkEPLp6 30og== 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=2WTGIgfPb8gHuOX0eUAFi/1Td8Fsoz17QczT+w+WBuY=; b=Rt17zS6oOr5Qg2u7w/laiQFIkIo2Vi1iFvSgBaBWiviDhm4flwskWtdLdyo7KULxOK vTleVV6tRfZ9TNYsgOlsPU418/0SmkL6qzyjYJxaVukTSut18YBGseMWzvcvMTZqN6sK QbCjtubrr3xJapwqzNA3J0k9c4gKGmSVo4OhO6ps9lSk0F8Fs2cPzFRVve3Mv4tmtmSp kpfU4O9ydbWaqzQTEjcBCRNJ2WSmhJEZ8i0PmIvTrUQ5ShpMrfZgS4IJf9C5E7ZWxkbo YBUVa38MUW4ZhFPv9kn5OFlogGM8b6p1iZeDrBFX1M6/4Rkn1jpig0xfjVA2cDwCF0UC tiqQ== X-Gm-Message-State: APjAAAVMNUuaEgmakrMpzXGtSG0VGHdyxXHOvmyXEI33YonkzlmCxw7C J0UNDKfFD8yl7vCAld8JKt4= X-Google-Smtp-Source: APXvYqzkz6gDIouPVC2d7Cu0YjyxEysVWB8H7r1jxAAOb1KD5Qktp8UyoK/vM1Toh3ZuUYgCO/POcg== X-Received: by 2002:a7b:cd84:: with SMTP id y4mr6757690wmj.79.1561716760672; Fri, 28 Jun 2019 03:12:40 -0700 (PDT) Date: Fri, 28 Jun 2019 11:12:38 +0100 From: Stephane Chazelas To: Bart Schaefer Cc: Oliver Kiddle , justindorfman@gmail.com, Zsh Hackers' List Subject: Re: Logo Message-ID: <20190628101238.dscl5mryiilbh5ib@chaz.gmail.com> Mail-Followup-To: Bart Schaefer , Oliver Kiddle , justindorfman@gmail.com, Zsh Hackers' List References: <95208-1561675878.358761@oOx4.pGSX.EcaY> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20171215 2019-06-27 16:20:31 -0700, Bart Schaefer: [...] > Now that you mention it, I'm curious how orange and black got chosen > in the first place? Is it because zsh was invented at Princeton? [...] Sorry for throwing a completely unrelated idea late to the party, but when the idea of a new zsh logo was first mentioned, one thing that came to my mind was a "ZSH" made with multicolor lego bricks to reflect the multi-faced, modular nature of zsh (and it can be shaped any way you want; playdough would also work there I guess). Maybe not the best image for a shell as lego bricks may convey some "building" meaning which do not as directly apply to a shell as to other tools. -- Stephane