On 1/9/18 6:19 PM, Nat! wrote:
> Chet Ramey schrieb:
>> On 1/6/18 8:14 AM, Nat! wrote:
>>
>> It's not incorrect; --norc is intended to suppress execution of the
>> interactive shell startup files, even if you specify another file to not
>> execute.
>
> Without any warning ? The man of the --norc o
Chet Ramey schrieb:
On 1/6/18 8:14 AM, Nat! wrote:
It's not incorrect; --norc is intended to suppress execution of the
interactive shell startup files, even if you specify another file to not
execute.
Without any warning ? The man of the --norc option specifies exactly
which files it is not r
On 1/6/18 8:14 AM, Nat! wrote:
> I tried to come up with a workaround, but I couldn't find any.
>
> Basically what I do:
>
> env -i bash --norc --noprofile
>
>
> This gives me an interactive shell, with a very clean environment (even no
> PATH), that does not contain system specify "surpris
I tried to come up with a workaround, but I couldn't find any.
Basically what I do:
env -i bash --norc --noprofile
This gives me an interactive shell, with a very clean environment (even
no PATH), that does not contain system specify "surprises".
This works.
But what I really want is to
On Tue, Jan 2, 2018 at 3:05 PM, Nat! wrote:
[...]
> Description:
> The documentation states, that /etc/bash.bashrc should not be read
> (rightfully so IMO) with
> --rcfile.
FWIW, there are two things going on here:
(1) /etc/bash.bashrc is actually disabled by default in the upstream
bash
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACK
