[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.b

From: Greg Wooledge
Subject: Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.bashrc?
Date: Wed, 29 Mar 2017 10:26:14 -0400
User-agent: Mutt/

On Wed, Mar 29, 2017 at 04:10:14PM +0200, Torka Noda wrote:
> Well, sorry for the confusion, I'll stop here. I think it's
> weird for Bash's positional parameters, and the whole argument
> list if modified with '-s', not to be accessible from
> initialization files, but `env` does what I want relatively
> simply compared to the tricks used by other people on the web,
> and I'll be content with that.

I'm still unclear on what you actually wanted to achieve.  Bash doesn't
normally *receive* any arguments when it's invoked as an interactive
shell, because the things that would invoke it are usually terminal
emulators that simply execute $SHELL, or shell escapes from terminal
programs like vi, which again simply execute $SHELL.

Specifyng behavior through environment variables seems sensible to me.
They're one of the few things available to interactive shells, being set
in your X session initialization, or your login profile, and then passed
down *through* your window manager, or your terminal-based editor/mail/news
reader, or both.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]