devcontainers / devcontainers/features
common-utils bash_prompt overrides ~/.bash_aliases
- 主要言語
- Shell
- スター
- 1.5k
- フォーク
- 622
- 平均マージ
- 6日 53分
- マージ済み PR(30日)
- 9
説明
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).
コントリビューションガイド
調査の方向性
common-utils コンテナ機能の bash_prompt セットアップを特定し、~/.bashrc への追記方法と ~/.bash_aliases との相互作用を確認します。ユーザーの dotfiles を変更せずにその動作を無効化できるオプションを追加し、そのオプションが有効な場合に既存の prompt 設定が維持されることを確認します。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- bash
- 領域
- devops
- issue の種類
- 機能追加
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 42/100