Re: Long standing annoying issue in ghci

2017-12-05 Thread cheater00 cheater00
A simple example of colored prompt would be good enough, so as not to make the docs too huge. People will be able to figure out they need \STX, or just make sure to tell them. On Tue, 5 Dec 2017 23:17 Brandon Allbery, wrote: > It's indirectly already there: >

Re: Long standing annoying issue in ghci

2017-12-05 Thread David Feuer
It sounds like this should be added to the GHCi documentation, even if it's not strictly about GHCi. David FeuerWell-Typed, LLP Original message From: Evan Laforge Date: 12/5/17 4:49 PM (GMT-05:00) To: Brandon Allbery Cc:

Re: Long standing annoying issue in ghci

2017-12-05 Thread Evan Laforge
Here's what I use: :set prompt "\ESC[46m\STX%s>\ESC[39;49m\STX " I believe \STX is a signal to haskeline for control sequences. Documentation is here: https://github.com/judah/haskeline/wiki/ControlSequencesInPrompt On Tue, Dec 5, 2017 at 12:57 PM, Brandon Allbery wrote: >

Re: Long standing annoying issue in ghci

2017-12-05 Thread Brandon Allbery
On Tue, Dec 5, 2017 at 12:36 PM, cheater00 cheater00 wrote: > without color coding the prompt so I can't really turn it off. It > seems like a simple arithmetic issue somewhere in the readline > implementation. > It's not arithmetic except in the sense that it's not doing

Long standing annoying issue in ghci

2017-12-05 Thread cheater00 cheater00
Hi guys, this one seems to have gotten buried under more important things, but maybe someone would like to take a look at it none the less? I've been encountering it literally every day for the last 4 years. I sometimes find it difficult to find read the past commands without color coding the