Joachim Schmidt

I'll reopen this issue to because there seems some support for this.

That's a great idea! Do you think amending the `Linenoise.linenoise` to include an optional parameter set (similar to `std.heap.GeneralPurposeAllocator` would be an acceptable solution? I'll also consider defaulting the file...

Ok, putting it in the `Linenoise` struct is a good idea. How should the responsibility of closing the file descriptors be handled? If the pattern is to assign to the...

I prefer the `File` approach. Although using a `Reader` and `Writer` would enable testing of linenoize, it imo creates a big footgun where users of linenoize may pass a buffered...

I've added `zig-package` to the GitHub tags.

I personally don't think arbitrary changes to the input buffer on normal keystrokes is intuitive for users. Normal keystrokes (all input except cursor movement, tab, enter, backspace, etc.) should have...

Currently, we don't have functionality for displaying all possible completions in a nicely formatted list on-demand (similar to bash on-demand completion of files in the current working directory or executables...

Counter-proposal which works with #10 as well: ```zig std.debug.print("this is normal text {this is also normal} {this is red}", .{ Style.default, Style{.foreground = Color.red} }); ```

This is of course convenient for enabling applications to have colored terminal output. But I think this library should also be robust and still provide the low-level interfaces like `updateStyle`...

Another counter-proposal: I think the most common use case for this high-level printing would be in association with compile-time known styles. This means we can design a function ```zig pub...