{"push_id":857888419,"size":1,"distinct_size":1,"ref":"refs/heads/patch-1","head":"39b0bf20f21fe949b6965df816e75c26557ab558","before":"e44aa50301cbdb9c713193263e6c0c5a9a5798c0","commits":[{"sha":"39b0bf20f21fe949b6965df816e75c26557ab558","author":{"email":"ab79dfe6cd87cc9cc78efb5adc7d12c157ac70cb@users.noreply.github.com","name":"Justin Puah"},"message":"Dynamic generation of mix commands for zsh completion.\n\nI wrote my own zsh completion file for mix today. I realised that depending on the project the mix tasks can change because of dependencies like phoenix or ecto.\r\nE.g. usually you wouldn't have 'mix phoenix.server' except in the project directory for a phoenix web app.\r\nThis is my solution for \"dynamic\" generation of the _1st_arguments:\r\nSo, I replaced most of the _1st_arguments with just \r\n\r\n    \"${(@f)$(mix help | egrep \"^mix \" | tail -n+2 | sed 's/^mix //;s/\\s\\+#\\s/:/')}\"\r\n\r\nThe above line will allow the zsh user to autocomplete all available mix tasks. I just finished this and thought I should submit it for other oh-my-zsh users.","distinct":true,"url":"https://api.github.com/repos/jinyeow/oh-my-zsh/commits/39b0bf20f21fe949b6965df816e75c26557ab558"}]}