Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Would you consider supporting PowerLine-like custom prompts?
See original GitHub issueI’m a big fan of Oh My Posh custom prompts and have customized my PSRL PromptText and ContinuationPromptText options like so:
Set-PSReadLineOption -ContinuationPrompt "`e[48;2;88;88;88m `e[0m`e[38;2;88;88;88m$([char]0xE0B0)`e[0m "
Set-PSReadLineOption -PromptText "`e[38;2;88;88;88m$([char]0xE0B0)`e[0m "
Looks a bit barbarian but it gives me a nice prompt like this:
Description of the new feature/enhancement
The problem with customizing the PromptText option with ANSI escape sequences is that this prevents the default processing in RenderErrorPrompt behaviour to kick in. It would be awesome if PSRL would behave like this:
Proposed technical implementation details (optional)
I would like to propose an additional option named ErrorPromptText that could be customized.
If set to a particular value, it would take precedence over PromptText being rendered in red and would be written as is.
What do you think?
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@mattcargile SOON™️ 👀
https://user-images.githubusercontent.com/2492783/154807780-3769846f-6ade-4b82-a679-a283d492449f.mp4
@mattcargile Sorry, obviously our PM team didn’t get the bandwidth to do this. I have added this issue to the “Features-for-Blogging” milestone to track it for the future blogging work.