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
[Question]: willing to make vterm into a separate lib? #20
Comments
Absolutely! I plan on refactoring 3mux this week after receiving some helpful bug reports. I'll use that as an opportunity to make vterm usable on its own. For the foreseeable future, I think most vterm bugs will be found through 3mux. It would be helpful to share an issue tracker between 3mux and vterm (with special tags to specify which of the two is broken). For this reason, would it be okay if vterm remains under this repo, but importable on its own via Either way, I'll make sure vterm's gets some documentation love. |
That’s perfect assuming it can be treated as public api. Happy to consume
and patch it this way.
…On Sun, Apr 12, 2020 at 2:28 PM Aaron Janse ***@***.***> wrote:
Absolutely! I plan on refactoring 3mux this week after receiving some
helpful bug reports. I'll use that as an opportunity to make vterm usable
on its own.
For the foreseeable future, I think most vterm bugs will be found through
3mux. It would be helpful to share an issue tracker between 3mux and vterm
(with special tags to specify which of the two is broken).
For this reason, would it be okay if vterm remains under this repo, but
importable on its own via github.com/aaronjanse/3mux/vterm?
Either way, I'll make sure vterm's gets some documentation love.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAET25CWQOI3PXHZEO3VODRMIXBPANCNFSM4MGSAHUA>
.
|
Does this sound good for a rough idea for a vterm API?
|
This would be great! May I suggest using a |
I've already got you covered 😉 Line 30 in 4389436
|
A not-yet-stable |
Thanks for putting this together!
…On Fri, Apr 24, 2020 at 11:28 AM Aaron Janse ***@***.***> wrote:
A not-yet-stable vterm package is available in v0.3.0. See fuzz/main.go
for example usage.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAET25BIXJEPRHI7LLYZMLROHK4JANCNFSM4MGSAHUA>
.
|
I'm curious, I have a couple of tools which could benefit from a comprehensive virtual terminal.
Thanks!
The text was updated successfully, but these errors were encountered: