https://github.com/AmrEldib/cmder-powershell-powerline-prompt

Custom PowerShell prompt for Cmder on Windows
https://github.com/AmrEldib/cmder-powershell-powerline-prompt

cmder powerline powershell prompt

Last synced: about 2 months ago
JSON representation

Custom PowerShell prompt for Cmder on Windows

• Host: GitHub
• URL: https://github.com/AmrEldib/cmder-powershell-powerline-prompt
• Owner: AmrEldib
• Created: 2017-03-21T02:41:48.000Z (almost 8 years ago)
• Default Branch: master
• Last Pushed: 2019-02-01T16:22:21.000Z (almost 6 years ago)
• Last Synced: 2024-08-01T13:37:04.082Z (5 months ago)
• Topics: cmder, powerline, powershell, prompt
• Language: PowerShell
• Size: 47.9 KB
• Stars: 97
• Watchers: 5
• Forks: 15
• Open Issues: 5
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# cmder-powershell-powerline-prompt

Custom prompt (and other configurations) for PowerShell in [Cmder](http://cmder.net/).  

![Screenshot](Screenshot.png)

## Aliases

Store aliases in `profile.d` folder. To easily manage aliases, create each alias in its own file with extension `.alias.ps1`.  

To store a private alias that you don't want to include in the repo, create it with extensions `.private.alias.ps1`.  

There's a special alias for quickly jumping to favorite folders: `goToFolder.alias.ps1`.  

Favorite folders are listed in the file `goToFolder.config` under `profile.d`.  

This file is a comma-separated file that lists an alias to a folder along with its target.  

For example: `c` sends me to `~\Code`.  

To use this command, I can simply type `g c` to go to `~\Code`.  

To add additional folder aliases, simply add additional entries in the `goToFolder.config` folder.  

See `profile.d\goToFolder.config.example` for example.  

## Setting up files in Cmder config folder

It's better to store the files of this repo in its own folder so that it can be updated easily without messing up other files.  

However, user profiles files must be reside in `%CMDER%\config` folder. We can use symlinks to get around that.  

Create symlink to `user-profile.ps1`  

```powershell

new-item -path c:\bin\cmder\config\user-profile.ps1 -itemtype symboliclink -value \cmder-powershell-powerline-prompt\user-profile.ps1

```

Create symlink to `profile.d` folder  

```powershell 

new-item -path c:\bin\cmder\config\profile.d -itemtype symboliclink -value \cmder-powershell-powerline-prompt\profile.d

```

# Status & Contribution

I published this code because it's not nice to keep it to myself. I fix problems that I encounter, and try to fix problems that others encounter if I have time.   

This code is provided with the timeless __Works on my Machine__ gurentee.  

You can also check out the [pull requests page](https://github.com/AmrEldib/cmder-powershell-powerline-prompt/pulls) for contributions that didn't make back into this repo. These are fixes to problems I didn't encounter, or features not useful to me, but maybe useful to you.  

People are very kind and contribute back fixes and improvements.  

This section is to acknowledage their contributions and thank them. If you find their contributions helpful to you, please take the time to thank them directly.  

- [lennybacon](https://github.com/lennybacon) [#3](https://github.com/AmrEldib/cmder-powershell-powerline-prompt/pull/3)  

I'd like to thank all who share their code with everyone for their time and effort.