Zsh Mailing List Archive
Messages sorted by:
Re: Possibly a bug involving rcs flag on mac?
- X-seq: zsh-workers 44073
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Guðmundur Páll Kjartansson <gpk188@xxxxxxxxx>
- Subject: Re: Possibly a bug involving rcs flag on mac?
- Date: Tue, 19 Feb 2019 21:11:11 -0800
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- 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==
- In-reply-to: <CAAaMBvDV-bYMkf6E41gsSs1GwoUgQ8KwGxVKyycG0FURv7fKvg@mail.gmail.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- List-unsubscribe: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAAaMBvDV-bYMkf6E41gsSs1GwoUgQ8KwGxVKyycG0FURv7fKvg@mail.gmail.com>
On Tue, Feb 19, 2019, 3:05 PM Guðmundur Páll Kjartansson <gpk188@xxxxxxxxx
> 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
> 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.
Messages sorted by: