Skip to content
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

Git Branch Autocomplete #130

Closed
adamjford opened this issue Jan 29, 2014 · 13 comments
Closed

Git Branch Autocomplete #130

adamjford opened this issue Jan 29, 2014 · 13 comments
Labels
👆 clink Upstream issue in clink.

Comments

@adamjford
Copy link

Before switching to cmder, I was using ComEmu + Git Bash, and it had a feature where if you were typing a git command that expected a branch name, like git checkout <branch>, you could start typing the name of the branch and then hit Tab to autocomplete the name. (Or at least I believe it included that; I might have added that myself a long time ago but I don't recall doing so.)

It doesn't appear that cmder supports that out of the box. Is there a way to enable that or would that have to be a new feature?

Note: I'm using the MSYSGIT version of cmder.

@rmorrin
Copy link
Contributor

rmorrin commented Jan 30, 2014

I would be interested in this also. Love cmder, but miss this feature from the git bash prompt!

@dufferzafar
Copy link

👍

@samvasko
Copy link
Contributor

Oh, I am afraid you are at wrong address. All the git completion is done by clink.
You can see the relevant FAQ

I am sure somebody can figure that out! I would also like to see that.

@adamjford
Copy link
Author

Oh, whoops! Good to know.

In the meanwhile, I added Git Bash as a task in cmder's ComEmu like I did with my standalone ConEmu, and that seems to be working.

@samvasko
Copy link
Contributor

samvasko commented Feb 1, 2014

Relevant source would like to contribute! 💪

@lehnerpat
Copy link

this works for me in current cmder.

I use the Git Bash installed with regular Git for Windows and it worked out of the box.

@sweiss3
Copy link

sweiss3 commented Mar 29, 2014

Hey,
I've just created a .lua script for it, which works with regular CMD.

I'm a bit of a github newbie, so if you can tell me how to publish it, I'd appreciate it..

Thanks!

@dufferzafar
Copy link

@sweiss3 - The easiest way probably would be to upload the code as a gist.

Go to - https://gist.github.com/ . Paste your code. Save it as a public gist and share the link with us.

Just do it, already. 😄

@sweiss3
Copy link

sweiss3 commented Mar 29, 2014

Haha, alright - there it is: https://gist.github.com/sweiss3/9858452

Note that this is my first encounter with Lua so it could probably be re-written to perform better.

Enjoy!

@dufferzafar
Copy link

I just did a git checkout and everything works, yay!

Now you just have to fork the project, add your code (the file to the config folder), and generate a Pull request.

This might help: http://guides.github.com/overviews/forking/

Happy Git-Hubbing!

@sweiss3
Copy link

sweiss3 commented Mar 30, 2014

@dufferzafar Thanks! I've created a pull request for it: #174

@espiriki
Copy link

I'm using the 191012 [64] version and looks like it doesn't work when you use aliases.
If I do "git checkout branch-name" that works for me. But I have an alias "co" for checkout
If I do "git co branch-name" that doesn't work

@bachbach
Copy link

@espiriki here you can find a workaround: #1495

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👆 clink Upstream issue in clink.
Projects
None yet
Development

No branches or pull requests

9 participants