devcontainers / devcontainers/features

common-utils bash_prompt overrides ~/.bash_aliases

Open
#472 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
1.5k
Forks
621
Avg merge
2d 11h
Merged PRs (30d)
4

Description

Description of the issue:

The common-utils container feature is useful, but has some the annoying behavior of unconditionally write to the end of my ~/.bashrc. I'd personally like an option to prevent this behavior, in particular I use my own custom ~/.bash_aliases from my personnel dotfiles repository, in which I define my own PS1 (in general, I keep the default provided ~/.bashrc and just put my own preferences in ~/.bash_aliases) .
Since ~/.bash_aliases would normally be sourced at the very end of a well written ~/.bashrc (as is done in the default provided one) then ~/.bash_aliases should have precedence over any sourced files. But if I use the common-utils container feature, then I am forced to invoke some container lifetime script to bring back my .bashrc to what I want.

Personally, I really don't like verbose prompt string, nor command injection in prompts (they tend to be very slow). I don't have any use for fancy prompts and I'd prefer if the common-utils container feature would have an option to completely disable the bash_prompt feature and not write in any of my dotfiles. (I think appending to user dotfiles is not a good design choice in the first place).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.