[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: |
Torka Noda |
Subject: |
Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.bashrc? |
Date: |
Sat, 25 Mar 2017 18:35:12 +0100 |
On Sat, 25 Mar 2017 05:40:18 +0100
Torka Noda <kanito.tasoga@gmail.com> wrote:
>
> The problem is that while PS1=foo is available once Bash has
> finished initializing (i.e., from the command line), it is not
> available from my ~/.bashrc, during initialization.
>
I meant 1=foo, here and in the title... Sorry for the possible
confusion, it was really just a mistake here, not in my
experience of the issue reported.
- Is it normal for `bash -s foo` not to make PS1=foo available from ~/.bashrc?, Torka Noda, 2017/03/25
- Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.bashrc?,
Torka Noda <=
- Re: Is it normal for `bash -s foo` not to make PS1=foo available from ~/.bashrc?, Chet Ramey, 2017/03/25
- Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.bashrc?, Chet Ramey, 2017/03/28
- Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.bashrc?, Torka Noda, 2017/03/28
- Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.bashrc?, Chet Ramey, 2017/03/28
- Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.bashrc?, Torka Noda, 2017/03/29