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 71a0eb4f for ; Tue, 19 Feb 2019 23:05:14 +0000 (UTC) Received: (qmail 2596 invoked by alias); 19 Feb 2019 23:04:56 -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: 44069 Received: (qmail 29407 invoked by uid 1010); 19 Feb 2019 23:04:56 -0000 X-Qmail-Scanner-Diagnostics: from mail-it1-f177.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.100.2/25112. spamassassin: 3.4.2. Clear:RC:0(209.85.166.177):SA:0(-1.8/5.0):. Processed in 0.718443 secs); 19 Feb 2019 23:04:56 -0000 X-Envelope-From: gpk188@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.166.177 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=qlj2avQm7d/C6Sj8RbSJQdaKhbOjM7eEdgmH+wAz18A=; b=K36n+GK8OCh/eS/1MHAXBPy228A3WQmpJT8LsiKOJ6rce6ZWvgDWYTJlCL6Ipj+h7f y3e5zkZbsXQojTy/xEm5nEMULivegLwET02blw4uovjZMVKSjunUmlvlqAHBvMBPHOkT 9hZtVOBu7JA7BS4kH3f3pbvax00QB3wHTzFF/KCr0TFGyv4asKYHRSQS29+iYXgL/a11 AQm2a0/kEXNJ8/7iluQOb7ydMUBr23oO50ZzfiZJx0MZOpbVpoGl3zDcVpaCJuhoyoEP 8VsjuDkT7eedVpxyuLdWVmei7V5qxDinobkijLQhuaw6yUV5KYPMe+XqjvX+NmUOWrfZ d4PQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=qlj2avQm7d/C6Sj8RbSJQdaKhbOjM7eEdgmH+wAz18A=; b=ih/XAcl5wHkh1GL1uFK4vBKL6FHCxn4YJ/aRM3dlF3cK22hwD+m3wdaW4TJ4/wxE9S jpQFAPRLhbEVk3p3ocUepAjLEZeg7xqY0btTpy952XChQ0ywg6gfIYfMTl1AWNnPzBa9 BtPOHunfgYfGIj+843pl+abWwTnnSmLjeQON3kGX2yh619BYS9k33DqBZlH2r8yXbMSv WOGymlQBU2oqS2Hnlg6CY8gGgnlNuuhHaV2o7ZDCIdDR5SHywHoFV+Vnml6nvIiAye5h 3h0+cE8S9ljbShk5qpWlAmbcyc9a8pYFmNLunq+BPfAoMq8s5AjTiiiM8JG9zRqFe62C 6W9w== X-Gm-Message-State: AHQUAuYIynvvcazH+cW0dX3K0hHQtCTBYKw4bXETxEwSYbdErjl8wUtV H7JEMKJSe6RE3I/IctDyKkeYjlcxh77q/WSSre3WC6DV X-Google-Smtp-Source: AHgI3IbXchC2M8xWAq+c9mW+SdZ7CIbwCMgSLMiw3JYqFruVL+KntMEqQHxEvRm1txegduO3fbJSVIWhD9SrGf544WU= X-Received: by 2002:a24:1947:: with SMTP id b68mr3383958itb.121.1550617461356; Tue, 19 Feb 2019 15:04:21 -0800 (PST) MIME-Version: 1.0 From: =?UTF-8?Q?Gu=C3=B0mundur_P=C3=A1ll_Kjartansson?= Date: Tue, 19 Feb 2019 23:04:10 +0000 Message-ID: Subject: Possibly a bug involving rcs flag on mac? To: zsh-workers@zsh.org Content-Type: text/plain; charset="UTF-8" Greetings I have some strange buggy behaviour going on. If I run zsh in a bash terminal window, it will not run .zshrc: $ zsh If I instead do this: $ zsh --rcs ~/.zshrc Then it will run .zshrc ... but it will also exit immediately ... this happens even if I run it in interactive mode: $ zsh --interactive ~/.zshrc If I add the below lines to the top of my .zshrc file, I can clearly see the difference in having the --interactive flag ... but it exits immediately either way: echo "running zshrc" if [[ -o interactive ]]; then; print yes; else; print no; fi I am using zsh version 5.7.1 ... I also tried it with 5.6.2 and even 5.3 ... but no luck ... I tried doing the same thing on my friends mac ... and there it worked without any problems (just running zsh straight from bash) ... Any idea what the issue might be?