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 66f386f8 for ; Mon, 30 Sep 2019 00:34:14 +0000 (UTC) Received: (qmail 24495 invoked by alias); 30 Sep 2019 00:34:06 -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: 44794 Received: (qmail 13036 invoked by uid 1010); 30 Sep 2019 00:34:06 -0000 X-Qmail-Scanner-Diagnostics: from mail-vs1-f65.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.217.65):SA:0(-2.0/5.0):. Processed in 3.6048 secs); 30 Sep 2019 00:34:06 -0000 X-Envelope-From: sgniazdowski@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.217.65 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=pDSGwWIKS2IBDMAuOorX/tqKJoK1HZbi7NbRFlZuXGc=; b=PFLeJXoCPqTA253h9+EznI2/cZzcsgsik31tVE/esBHKJ3q9CeK0D3ngiMeQY/JwlO 6g2ogiK+4/HUCIuE5gCRuIHiWbFhe8Mq1OoXVYiV/AswY2t1Ugo4bp8zHxcisgGM4aUl eys5qrtTxsXgI7VyUsdLa1pbw79y4Cumd70b6v/Zv8l01wbhUsHicbg1DXkLOsmuvDno aeFZZZapIlRiiHMROlJ/Jgj4fb5o0ib+tZVI8OSTwHBxwgVykSiQClA0U0NUf31y55Lc eK49SsXg3TENMzsB62BeFUvNG9G+d8c0hRsnT+RF5oAW9LseaUw3CCCVQ8TJsn5GqPXs C9Ng== 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:content-transfer-encoding; bh=pDSGwWIKS2IBDMAuOorX/tqKJoK1HZbi7NbRFlZuXGc=; b=l9fQhFTHAtm3J9O974g5TyzsEPO4RZk0cYW7s5+e88OAbF7nCya0Pbiz2V1AydKERB WfvbyTRqfcys510oHAg+2GHd7j5/F2PzpgRG83QTc5rNm+2kE2s5BzyaDmXZLBLIlb3p osPabHHHJJ9B8JaYTypLkBUWg/hY5PmGA9eUOXol8Up8RT7OhahX6SNHEE1xufjUQduu AlyLWxkR6zQFK9v4d5+zfXpG9NXwJMmgvXZ4sQNEQgHy/S1ASsO9gJOq0KbXAWgO207I gocN/6NJj4CThvoVfHRPOycHyu7fNE+1c/VEgdONZ/BW6WgTcLHPGeMZiaj2ZA8rGQ2J POcQ== X-Gm-Message-State: APjAAAXusYyAfoFup8wTZ8rSQarom9BZICAK2YdB3rJ4y7b87vmXI2+P yA9p6AUliEFATj/314+FHjew8LQu5wVVc7Nvu8ZrkA== X-Google-Smtp-Source: APXvYqy4/oWm9Hqse9lkSTjSoa3qVzPuEmOHXLTjOTj4fTZ3n6F2LdpBaRmRgLoE2xSqJjz6Jt+dlOAWAuhQpieNJbQ= X-Received: by 2002:a67:f086:: with SMTP id i6mr8743855vsl.113.1569803609069; Sun, 29 Sep 2019 17:33:29 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sebastian Gniazdowski Date: Mon, 30 Sep 2019 02:30:46 +0200 Message-ID: Subject: Re: BUG: Random behavior of the shell To: Bart Schaefer Cc: Zsh hackers list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 30 Sep 2019 at 00:34, Bart Schaefer wro= te: > > 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 ... Ok, I'll remember the tip about the screen shots. The video is a proof that I'm not making things up, that the shell really does behave in an unpredictable manner. It also allows to go back and see what was happening after a time, like when you point later about the long vs. long long warnings from GCC. > > The list isn't getting filtered. > > > > Earlier was: the `quiet=3D1` 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.) I've minimized the test case, that's why I've removed a print -P from the conditional command. I think that the issues are related like when you state later =E2=80=93 by = a general problem. It's not the only random behavior that I've observed =E2=80=93 earlier my plugin zconvey just wasn't working, to then start work= ing without problems. I've now switched to own zsh build and the problems disappear, so it might be some problem with Mageia's build of Zsh. > > 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 think not, mine is Mageia 7. > 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? It seems that the warning is related to printf() format string. However I'm starting to think that this is a problem with a subtle build error in the Mageia's Zsh distribution. However, shouldn't such error reveal itself much more often? --=20 Sebastian Gniazdowski News: https://twitter.com/ZdharmaI IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin Blog: http://zdharma.org