From: ludo@gnu.org (Ludovic Courtès)
To: Roel Janssen <roel@gnu.org>
Cc: 29337-done@debbugs.gnu.org
Subject: bug#29337: Bash reads system-wide bashrc unconditionally.
Date: Tue, 21 Nov 2017 09:50:01 +0100 [thread overview]
Message-ID: <8760a4nhhi.fsf@gnu.org> (raw)
In-Reply-To: <87mv3gsjt6.fsf@gnu.org> (Roel Janssen's message of "Mon, 20 Nov 2017 22:48:37 +0100")
Heya,
Roel Janssen <roel@gnu.org> skribis:
> Roel Janssen <roel@gnu.org> skribis:
>
>>> On CentOS 7, the following happens (yes, I added the echo-statement to
>>> /etc/bashrc on CentOS as well):
>>> $ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
>>> Goodbye, world
>>>
>>> On GuixSD:
>>> $ env - bash --init-file <(echo "echo \"Goodbye, world\"") -i
>>> Hello, world
>>> Goodbye, world
> Well it seems that it isn't ignored when it ought to be ignored -> when
> specifying --init-file. This is a difference between how Bash works on
> CentOS 7, and how Bash works on Guix(SD). I can't find a
> user-configurable option to make it work the same as on CentOS 7.
Now, we’re compiling Bash with "-DSYS_BASHRC='\"/etc/bashrc\"'". I
wonder if removing that flag solves the --init-file case.
Ludo’.
next prev parent reply other threads:[~2017-11-21 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 12:16 bug#29337: Bash reads system-wide bashrc unconditionally Roel Janssen
2017-11-17 21:04 ` Ludovic Courtès
2017-11-20 21:48 ` Roel Janssen
2017-11-21 8:50 ` Ludovic Courtès [this message]
2017-11-24 15:46 ` Roel Janssen
2017-11-24 20:51 ` Ludovic Courtès
2017-12-11 11:35 ` Roel Janssen
2017-12-11 13:19 ` Ludovic Courtès
2017-12-11 15:31 ` Roel Janssen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760a4nhhi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29337-done@debbugs.gnu.org \
--cc=roel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).