Piotr Murach

@spikeheap The fact that bundler follows semver, at least in my understanding, means that current APIs won't break. However, this doesn't mean that internal APIs won't change including code refactorings....

Small update on this issue. I decided that I'm going to drop dependency on bundler all together and forge my own solution for scaffolding a brand new gem setup. It's...

@dbalatero I hope you won't give up on `tty`! Here's a little bit of update and plan: 1. Update all tty components(more than 20) and change bundler to 2.0: (in...

@bopm My plan is to start working on this from the next week. I cannot give you a deadline but my main focus will be on switching to Bundler 2...

@bopm To clarify. Don't let the Bundler version delay you. Bundler is only used to generate your CLI app structure - it isn't a dependency for a new project. To...

@DNA Thank you for the interest! I know it's a bit disappointing to still see this issue here. I can assure you that I'm annoyed as well. I'm painfully aware...

@cwant Thank you for your comment Chris. This issue is solved in the master branch. Unfortunately, the gem is not ready for release yet. I have a system where I...

@mike-yesware Thanks for you comment Mike. I appreciate your enthusiasm for making a new release. But the `tty` isn't ready to be released yet. It's not far away though. There...

@aovertus The `tty` gem is only used for scaffolding new CLIs and shouldn't be used as a direct dependency. Looking at the broadside gem source, you only use [tty-table](https://github.com/piotrmurach/tty-table) and...

That sounds useful, I would be interested in the api, do you have any code examples to show?