You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Directory path with truncated git repository name.
Additional context/Screenshots
To reproduce this behavior perform the following:
Clone a git repository (e.g. repo_one)
Create a directory inside the repository (e.g. foo)
Create a soft link outside repository to the newly created directory
ln -s repo_one/foo bar
Follow newly created soft link
cd bar
I was able to narrow down the absent directory ouput in the configuration. It seems to be related to repo_root_style option in directory module. As soon as I remove it, the current path is shown. However, it doesn't fix the problem with no git repo name truncation.
I included my current shell environment, fish, but same happens in bash as well.
Environment
Starship version: 1.11.0
fish version: fish, version 3.5.1
Operating system: Mac OS 12.6.0
Terminal emulator: iTerm.app 3.4.16
Git Commit Hash:
Branch/Tag:
Rust Version: rustc 1.64.0
Rust channel: release
Build Time: 2022-10-15 01:40:28 +00:00
Relevant Shell Configuration
ifstatus is-interactive
starship init fish | source
end
Starship Configuration
[directory]
repo_root_style = "bold green"
The text was updated successfully, but these errors were encountered:
Current Behavior
No directory path is shown at all.
Expected Behavior
Directory path with truncated git repository name.
Additional context/Screenshots
To reproduce this behavior perform the following:
cd bar
I was able to narrow down the absent directory ouput in the configuration. It seems to be related to
repo_root_style
option indirectory
module. As soon as I remove it, the current path is shown. However, it doesn't fix the problem with no git repo name truncation.I included my current shell environment, fish, but same happens in bash as well.
Environment
Relevant Shell Configuration
Starship Configuration
The text was updated successfully, but these errors were encountered: