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.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, 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 5aa2c90d for ; Sun, 29 Sep 2019 22:34:54 +0000 (UTC) Received: (qmail 1940 invoked by alias); 29 Sep 2019 22:34:49 -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: 44793 Received: (qmail 11518 invoked by uid 1010); 29 Sep 2019 22:34:49 -0000 X-Qmail-Scanner-Diagnostics: from mail-lj1-f177.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25587. spamassassin: 3.4.2. Clear:RC:0(209.85.208.177):SA:0(-1.9/5.0):. Processed in 2.611898 secs); 29 Sep 2019 22:34:49 -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.208.177 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eCg+O1uCSrujlVbRPnduSMlPbE/kKeLDpapXHT6GNe4=; b=dvCUeWnJfjp+f0T02S+4wVk0iiKpnUz9j216skW4Y+LX4ov4qCqWRiS94p9+W84Epb URwQiQOtCS1+LSbTOjIChY7Q5VUeXmY8M7jdE4GDPFhwGieDtEavryHcl9z5WCbZ7Wgv gZVWr5aV6u/t2Bb3fBBk7pp3LeEJHDcdd2b6SnSKJiuDyTTueoSaH9qTYPILNAHglmKK ETdjr2jZUoDVWh644LsRmMAsyG0raiev5rcUixfSeQPMShfs98wCQdoX2MNVc0pYtVDp PC3UVwm9rkzkhG3PfBYtr71vV9QKzhWwiJG5qzR6m8Mi852cx1QvuTE0l0fqOAzw1RO7 laLw== 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:cc; bh=eCg+O1uCSrujlVbRPnduSMlPbE/kKeLDpapXHT6GNe4=; b=VPgGxnsMJf/19neZLHj5lmJgaE2U29HtLSdfwI+ZTtXy8Hliy6o733baXoieN46Eaj /3g8kUWYYpumqDVNSBEV1laSnPNwE6bix/oHPD7AmahwADEGA6a+++EYixMveTTIGuGQ K6efQflP5YOpgU7RVZuL7996HZOyjZCvf+kfcWuDyHPFwxoEu2724+ZiCnw3lfP5rA3N WFr+EwcJ9sicadY3nmy003gbCXYErPRcbSHcdEL++2Hh4hEQw3eoRraoJJNdXAUi7dsA UYP3dEequc1U20zFDKhUrD9k1Zr0MzHaPlHBkKl2Jwg31nSKcHJAwfs/sKZX3Q2BBGJY ybhQ== X-Gm-Message-State: APjAAAUCL20OIbn0NdN/2Z+SEItonjXhpynQYncpA03tJ22ayO9/jzdg UGrtaEuxbslTwLQ+GtAxhSb1uX3NrZQbo8RitqU5Lw== X-Google-Smtp-Source: APXvYqyitxxLS8fUuZFqx7MUm+gzLMNUVUls2nMawSjy61+d0nF0O3GKGhj9hlwy9PndIwnknC7vuTwjxoebIRY5L8E= X-Received: by 2002:a2e:878c:: with SMTP id n12mr10095607lji.175.1569796451824; Sun, 29 Sep 2019 15:34:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Bart Schaefer Date: Sun, 29 Sep 2019 15:34:00 -0700 Message-ID: Subject: Re: BUG: Random behavior of the shell To: Sebastian Gniazdowski Cc: Zsh hackers list Content-Type: text/plain; charset="UTF-8" On Sun, Sep 29, 2019 at 2:03 PM Sebastian Gniazdowski wrote: > > I was getting such behavior earlier, but waited with the report. Now > it's a more clear one, so I'm reporting: https://youtu.be/N-HH2f_Rr0E It's really difficult to see what's going on with these recordings you keep posting. Video compression often makes them go by even faster than real-time, and when the list of results you're displaying more than fills the screen it's a pain to step backwards to see what you were doing before. If you must resort to visual aids, a series of still screen shots would be better. That said ... > The list isn't getting filtered. > > Earlier was: the `quiet=1` assignment in the below These don't seem very likely to be closely related problems. This most recent one looks like a pattern matching issue, the other looks like perhaps an exit status is leaking from one conditional test to another. Why do you have a [[ ... ]] standing all by itself as a command, with nothing testing the results? (Not that this should cause a bug.) > problems started when I've switched to Linux, so this could not be > connected to any recent commits. This isn't by any chance the same version of linux where Dennis is reporting problems with trap functions? I saw a "long long" vs. "long" error go by in compiler output in one of those videos. Could wordcode be getting messed up by a default integer byte-width in some circumstances, or something like that?