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

What's the difference between this package and comint-mime? #30

Open
hongyi-zhao opened this issue Jan 15, 2022 · 4 comments
Open

What's the difference between this package and comint-mime? #30

hongyi-zhao opened this issue Jan 15, 2022 · 4 comments

Comments

@hongyi-zhao
Copy link

hongyi-zhao commented Jan 15, 2022

It seems that this package aims to achieve a similar purpose as what done in comint-mime. What's the difference between this package and comint-mime?

Regards,
HZ

@riscy
Copy link
Owner

riscy commented Jan 15, 2022

Thanks for the question. I started this package over ten years ago and it looks like comint-mine is oriented around python. If you don't mind me asking, why do you ask?

@hongyi-zhao
Copy link
Author

If this package is more generic and robust than comint-mime to do things like the ones discussed here and here, then I might consider trying it out and switching eventually.

@riscy
Copy link
Owner

riscy commented Jan 17, 2022

I see! It's possible, but on a (very brief) look at comint-mime's code, there's much more going on there to handle python REPLs than shx -- the latter is sort of designed around targeting the command line shell as opposed to python REPLs.

@hongyi-zhao
Copy link
Author

If so, at least they can be used side-by-side to complement and make up for each other's shortcomings.

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

No branches or pull requests

2 participants