-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allowing path segment separator customization #1222
Comments
this is being worked on in #1209 |
Wonderful! Missed that PR, thanks for point it out! |
Given some interest, maybe this could be re-opened since #1209 died? |
That would be lovely. This is the one thing that keeps me from having a prompt similar to powerline: |
It would be nice to have the platform separator as a variable too so one could do: [directory]
truncation_symbol = "…$pathsep" |
almost 4 years have passed, any news here? |
I would be happy to rebase and update the PR #5030 if necessary |
That would be quite helpful I think; I'm sure maintainers would be more willing to review something that could be immediately merged. |
Feature Request
Is your feature request related to a problem? Please describe.
Currently there's no way to set the path segment separator, which would be useful for platform consistency and customization.
For example, Windows separates segments with
\
all around the OS, and even though in PowerShell you can tab-complete with a forward slash, it still changes it to a backslash.This is inconsistent, and at least to me it just doesn't look great!
Describe the solution you'd like
Adding an option to the Directory module would solve this problem. Without having given it much thought,
path_segment_separator
seems fitting (although maybe too verbose).This allows the user to choose whether they want to fit with their platform, gives them freedom to customize it as they see fit, and provides a sane default (
/
).And with
path_segment_separator = " > "
Describe alternatives you've considered
Platform detection
Ultimately this takes agency away from the user, and could introduce inconsistencies with how the platforms are actually detected. Adding an option feels more inline with this project.
Doing nothing
I've done this so far and it's still bothering me 😉
The text was updated successfully, but these errors were encountered: