-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Discuss: Completion for Mac Defaults - The one where he hunts down Janathon Mah #1924
Comments
Why hello!
I'm happy to add it under my user for it to be vended from. For 5+ years I've switched to using fish shell so don't have any personal incentive to work on the bash ones. I don't have any updates, but I'm happy to incorporate them. Is there a preferred repository layout for the vendored repositories? Looking at https://github.com/Bash-it/bash-it/tree/master/vendor/github.com it seems like there's a mix, with some having the completion file at the top-level. |
Hey @jmah thanks so much for replying ! re: Repository Layout I think the The other two, Although the goal here is to capture So I'm thinking the layout might be something like one of these: repo: bash-completions
or, if mac-specific: repo: bash-completions-mac
Q: Do you have personal (ie. official) copies of your old completions? I believe the version that bash-it contains was modified (and I believe broken) at time of first commit. I have a version that I extracted from the old bash-completion gist linked in my other post, which I can provide if you don't have your old copies around. Other Differences The version in the wild differs from the bash-it version in another way:
i.e the I understand if you feel strongly about keeping that logic, i.e. capturing the actual version of your script in your repository. If so, we would likely comment out that code in our version at time of vendoring. Thank you again for replying, and please let us know your thoughts on this and how you might like to proceed. Cheers! -DF |
@jmah Just wanted to give you some closure on this. @gaelicWizard has agreed to take ownership of the completion, vendoring it out into one their repos. As they still use it regularly and are making enhancements, I think it's a great outcome. Thanks a lot for chiming in and good luck out there! -DF |
@NoahGorny wrote:
With some googling and help from the WayBack machine, I tracked down the infamous
"Jonathon Mah"
:Below are some links where I found versions of the completions in the wild.
Interesting to note is that the original version that @tswicegood committed in 2012 differs from these other versions in a significant way:
You'll notice the original version uses the
@(${cmds// /|})
technique that I mention on #1922We could put a PR together to revert to this original version, but I have higher hopes:
@jmah Would you be interested (willing) to re-take control of this completion as a repo in your github profile, and then we could Vendor it back into bash-it from there? Additionally, do you happen to have any new updates to it?
Thanks,
-DF
cc: @jmah , @tswicegood
Discovered links for posterity:
https://lists.apple.com/archives/xcode-users/2006/Nov//msg00174.html
Mentions xcodebuild and defaults completions being hosted at:
http://www.playhaus.org/mac_bash_completion
https://sourceforge.net/p/fink/mailman/message/27426751/
A version of the completions incorporated into Fink 2011-04-28
https://gist.github.com/mbauman/839902
A gist for patching the completion (among others) into Bash-Completion 1.3
This version is an exact match to the Fink version above
The text was updated successfully, but these errors were encountered: