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

ConEmu integration information will open two tabs #178

Closed
davidovich opened this issue Jun 1, 2015 · 4 comments
Closed

ConEmu integration information will open two tabs #178

davidovich opened this issue Jun 1, 2015 · 4 comments

Comments

@davidovich
Copy link

I want to configure ConEmu to open a new tab (task) and if I follow precisely the documentation in commit ac6b03c (linked from the release notes of 2.4.2.1) to integrate git bash in ConEmu (v150513), the result is that two tabs get opened:

  • one for parent task called git-bash with the following contents:
    GUI application (PID=xxxx was attached to ConEmu:
    C:\Program Files\Git\git-bash.exe
  • another tab with the expected mingw64 bash shell

I would expect to have only one tab opened.

The process tree shows that a new parent ConEmu is started...

image

Is it possible to detach from the git-bash launcher ?

@dscho
Copy link
Member

dscho commented Jun 9, 2015

@Maximus5 your help would be much appreciated here.

@dscho
Copy link
Member

dscho commented Jun 11, 2015

@dscho dscho closed this as completed Jun 11, 2015
@davidovich
Copy link
Author

Verified fixed in ConEmu 150610

@dscho
Copy link
Member

dscho commented Jun 15, 2015

@davidovich thanks for following up!

jeffhostetler pushed a commit to jeffhostetler/git that referenced this issue Aug 30, 2019
…reamable version

I'm creating this PR for a fourth time (see git-for-windows#163, git-for-windows#171, and git-for-windows#178 for earlier versions). This version is tracking my progress to create something that can be sent as an RFC upstream, but also can be used to start the sparse feature branch. This is based on v2.23.0.

Note: I currently have conflicts with the virtual filesystem feature, and I'll resolve those with a merge commit when I'm ready. I'm just creating this for tracking progress at the moment, but can also be a place for early feedback.

* git sparse-checkout disable to disable the sparse-checkout feature and return to a full checkout.
* git sparse-checkout init --cone, to initialize in cone mode.
* git sparse-checkout add when core.sparseCheckout=cone.

This includes performance improvements with the hashset-based matching algorithm, but I'll leave further enhancements as smaller steps on top. Here are a few things I want to try:

Track the maximum depth of a prefix pattern, so we know to not run hashes for deeper paths.
Use the "known exclude" bit in cone mode to stop hashing paths we know will not be included.
Use the "known include" bit in cone mode to stop hashing paths we know will be included. This is more difficult than "known exclude" because we need to distinguish directories from files when doing path matches so we don't give a directory a "known include" when it isn't a recursive pattern match.
jeffhostetler pushed a commit to jeffhostetler/git that referenced this issue Sep 30, 2021
This version allows us to update existing `winget` manifests by
specifying a manifest's SHA if it already exists in `microsoft/winget-pkgs`.

Pull Requests
---------------

* [git-for-windows#178](mjcheetham/update-winget#179): Allow
updates to existing winget manifests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants