Skip to content
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

conque does not display ghci prompt #24

Closed
GoogleCodeExporter opened this issue Feb 25, 2016 · 4 comments
Closed

conque does not display ghci prompt #24

GoogleCodeExporter opened this issue Feb 25, 2016 · 4 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. :ConqueTerm ghci

What is the expected output? What do you see instead?

expected output is:

GHCi, version 6.12.3: http://www.haskell.org/ghc/  :? for help
Loading package ghc-prim ... linking ... done.
Loading package integer-gmp ... linking ... done.
Loading package base ... linking ... done.
Loading package ffi-1.0 ... linking ... done.
Prelude>  

but conque does not display "Prelude>" prompt.

What version of the product are you using? On what operating system?

revision 332, linux amd64

Please provide any additional information below.

Attached file is conque DEBUG log outputs.

It's seems that conque treat string '\x1b=Prelude> ' as unknown escape sequence 
and ignore this.

Original issue reported on code.google.com by arumaka...@gmail.com on 21 Sep 2010 at 4:12

Attachments:

@GoogleCodeExporter
Copy link
Author

Thanks for the report. I don't have GHCi installed on this machine, but r333 
should fix it.

Original comment by nicora...@gmail.com on 21 Sep 2010 at 5:05

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

I update to r333, but this time conque displays escape sequence "\x1b=" too.

So I tried to write patch to fix this issue.
Attached patch make CONQUE_SEQ_REGEX to match "\x1b=" and "\x1b>", so they will 
be treated as escape sequence.

Could you review this patch? Thanks.

Original comment by arumaka...@gmail.com on 21 Sep 2010 at 6:23

Attachments:

@GoogleCodeExporter
Copy link
Author

Try r334. It should be the equivalent of your patch.

Original comment by nicora...@gmail.com on 21 Sep 2010 at 8:25

@GoogleCodeExporter
Copy link
Author

r334 fix the problem. Thanks!

Original comment by arumaka...@gmail.com on 21 Sep 2010 at 10:26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant