-
Notifications
You must be signed in to change notification settings - Fork 94
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
Expose tailspin
as a crate / library
#118
Comments
Perhaps my question will help identify requirements and api for a tailspin library. Since tailspin is normally used as a shell program, with options, stdin/stdout, and file configuration largely according to local, interactive cli needs; how would tailspin be used as library, or what context and benefit would a library serve over manual binary execution, or basic scripted automation? Eg, if you are developing a log monitoring application and want to integrate the library, how would the library use make local implementation easier for arbitrary other sites? How would a library be worth the effort? AI generated clarification: Tailspin is typically used as a shell program with command line options, standard input/output streams, and configuration via files to support interactive use cases. What value would a tailspin library provide over just executing the tailspin binary manually or via scripts?
|
I'd definitely like to see this happen. Taking a read through the source, I can see why it's not a trivial task to do like the linked PR. The CLI-ness seems to invade quite a few of the types and methods. To name a few:
I think what might work for this is to make a |
Expose the highlighting functionality of
tailspin
as a crate / library to enable easier integration with other Rust programs.See for example:
#116 and zifeo/whiz#117
The text was updated successfully, but these errors were encountered: