{"push_id":730036892,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"ddf84a5577fa1b7341dd404bdf5b5e9b9a43cf72","before":"2616fe2bbe55feb0048e3e973966f83d7f5f9710","commits":[{"sha":"2754b092d854066854ef019ab4f2ca8b1d37e43e","author":{"email":"f0bc0b0d596e4254a986b9422ebd9c789c7f2f0c@gmail.com","name":"toejough"},"message":"Summary: Fixes #7 - tab support\n\n**Problem:**\nNo support for catching tabs\n\n**Analysis:**\nTab-completion is a common thing to do with low-level input CLI control.\nWe should enable it by allowing users to catch when the tab key is\npressed.\n\nReturn 'TAB' instead of a character.  This is generally a control, along\nthe same lines as 'enter', and arrow keys, home key, etc.  At least,\nthat's the use case being targeted.  Returning a whole string is\noverloading the idea of a \"key\", but it's lighter-weight than returning\nan object you have to parse for every key.\n\nI might still implement things that way in the end (objects), but I'm\nnot going to until necessary.  Using a string is still unambiguous\nenough, because other characters are single characters, rather than\nstrings, and even multi-char unicode \"characters\" are not going to\noverlap with the strings being used ('TAB', 'UP', 'DOWN', etc).\n\n**Testing:**\nAdded a test which uses the '\\t' key, as well as the control-i combo.\n\n**Documentation:**\nAdded description of return value for tab.","distinct":false,"url":"https://api.github.com/repos/toejough/ugetch/commits/2754b092d854066854ef019ab4f2ca8b1d37e43e"},{"sha":"ddf84a5577fa1b7341dd404bdf5b5e9b9a43cf72","author":{"email":"f0bc0b0d596e4254a986b9422ebd9c789c7f2f0c@users.noreply.github.com","name":"toejough"},"message":"Merge pull request #24 from toejough/issue.7.tab-key\n\nSummary: Fixes #7 - tab support","distinct":true,"url":"https://api.github.com/repos/toejough/ugetch/commits/ddf84a5577fa1b7341dd404bdf5b5e9b9a43cf72"}]}