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=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 f73ff211 for ; Wed, 20 Feb 2019 05:12:17 +0000 (UTC) Received: (qmail 16038 invoked by alias); 20 Feb 2019 05:12:02 -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: 44073 Received: (qmail 9109 invoked by uid 1010); 20 Feb 2019 05:12:02 -0000 X-Qmail-Scanner-Diagnostics: from mail-lf1-f53.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.167.53):SA:0(-1.9/5.0):. Processed in 2.263037 secs); 20 Feb 2019 05:12:02 -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.167.53 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=vOcgkzr7JWpXXyCSjGrJc283yN2n35TckHwKogm078Q=; b=x4D7glcrUDWYm4glUkMvjiD1p30b+MuUJFWdW4l8Kd67rNNXzsjBHQxQmmR6myS8ix 4wuOoyE0VqAekQa/qJ22OBt3wTzkmhsTtemSfFauSk02yIuaQ9IGDvafJfUNMVN6jlx+ MrYSWC5Bo61hou1i1HP3aMdXQW6ws80cojXX2AmLImQym4uz97xfu35U7rehKW5PAl/1 s2dJZkntbkBRyWAxfKlY/7ZPN3en16BHYdhXMoq89iq9BP5Tfb4L8Puduww6f07CK5qz 2J0kJiykgJPsOE4ciUpfOvcrPDmtb0skVuK3Z3NiBaxkOGalmTFZa0n/N8iChfkOFij2 6Jqg== 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=vOcgkzr7JWpXXyCSjGrJc283yN2n35TckHwKogm078Q=; b=av+Fi3wa/RgtqJ4Tu2XstdWx8K+heZHzHywGFlXEwOFgU2ban+Gth2Cgdec3TTY04K hL1y2XvaEeR/SUsTChxqmF0ICxpk7IDfgCgJuFVhlr+Kh4lTL+ZxpKZAzsATJsPBPi3d uftTa3cQH43rNsDjIw8NtFZEAaQDAzSlegrpHjrHM52WYzQ7KO0dSL9Ze7ylF/ULnjVi 7M+niVmRrx3WQFkoy/vNAZUHSj1AXuuMrMClsAt+sms23cdhj3jSnF/17JZ6VoC5Jtzw SilkN/Ids0acFvKhILxvrR4z8jSLELg+UVVLtB8fTacJWbCmfOIv2McSmItwPhlBW86Y 0oMw== X-Gm-Message-State: AHQUAub1wswRtslKaCj2YDW6XyKshtb9NZSGekj1C3EUehIQLq9tf9HA jDzOHREjH1HKvjTFX9/TGYnBbh5rK3fsf0b0/G9NmQ== X-Google-Smtp-Source: AHgI3IagAx/nAfkOEZoxqoy2Vlar1VUIB4bpPjl+gibzXUuARFwZDZsu0PlPj/nSJIshdEBIji6Nyc0LGhMb/mB2WkM= X-Received: by 2002:ac2:52b7:: with SMTP id r23mr20297771lfm.66.1550639484653; Tue, 19 Feb 2019 21:11:24 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Bart Schaefer Date: Tue, 19 Feb 2019 21:11:11 -0800 Message-ID: Subject: Re: Possibly a bug involving rcs flag on mac? To: =?UTF-8?Q?Gu=C3=B0mundur_P=C3=A1ll_Kjartansson?= Cc: Zsh hackers list Content-Type: multipart/alternative; boundary="000000000000a86da905824c63bf" --000000000000a86da905824c63bf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Feb 19, 2019, 3:05 PM Gu=C3=B0mundur P=C3=A1ll Kjartansson Greetings > > I have some strange buggy behaviour going on. If I run zsh in a bash > terminal window, it will not run .zshrc: > > $ zsh > I'm not sure what to say about that; is it possible that $HOME is set incorrectly or that $ZDOTDIR is set? Does zsh appear otherwise to be interactive, i.e., it prints prompts and ZLE is working? If I instead do this: > > $ zsh --rcs ~/.zshrc > > Then it will run .zshrc ... but it will also exit immediately You have misunderstood how the shell options work. If you give the shell a file name as an argument, it reads that file for commands and then exits. The --rcs option does not change that, it merely says that it's OK for the shell to read the usual startup files as well (where "usual" depends on whether the shell is interactive, is a login shell, etc.). --rcs is the default, so ordinarily one would be using --norcs to turn them off instead. ... this > happens even if I run it in interactive mode: > > $ zsh --interactive ~/.zshrc > Yes, even if the shell is interactive a filename argument means to read the file and exit. To force the shell NOT to read commands from the argument file, you must use the --shinstdin option. There is no simple way to cause the shell to first read a file and then continue reading from stdin / the terminal. --000000000000a86da905824c63bf--