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

Build 150910 breaks git on windows #341

Closed
OverlordQ opened this Issue Sep 25, 2015 · 24 comments

Comments

Projects
None yet
3 participants
@OverlordQ

OverlordQ commented Sep 25, 2015

Default CMD:

C:\projects\project>git add -p
No changes.

ConEmu wrapped cmd:

user@host C:\projects\project
> git add -p
fatal: Not a git repository: . at /usr/lib/perl5/site_perl/Git.pm line 210.
@OverlordQ

This comment has been minimized.

OverlordQ commented Sep 25, 2015

Working: 150908
Broken: 150910

@OverlordQ OverlordQ changed the title from New build breaks git on windows to Build 150910 breaks git on windows Sep 25, 2015

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Sep 25, 2015

  • git version?
  • What if you run "ConEmu -basic -cmd {cmd}"
@OverlordQ

This comment has been minimized.

OverlordQ commented Sep 25, 2015

Tried multiple versions of git, unsure what first ver was, but testing git version 2.5.3.windows.1 now.

~~~Spawning a new conemu with '-basic' seems to fix it.~~~

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Sep 25, 2015

Spawning a new conemu with '-basic' seems to fix it.

That's interesting. I use git on daily basis and do not see problems. What option breaks your behavior?

@OverlordQ

This comment has been minimized.

OverlordQ commented Sep 25, 2015

I stand corrected, I forgot to switch back to the x13 build. Running with -basic still exhibits the broken behavior.

> git add -p
fatal: Not a git repository: . at /mingw64/share/perl5/site_perl/Git.pm line 211
@Maximus5

This comment has been minimized.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Sep 25, 2015

Also, can you please create debug log files for Shell mode during execution of git add -p?

http://conemu.github.io/en/SettingsDebug.html

@OverlordQ

This comment has been minimized.

OverlordQ commented Sep 28, 2015

Here's the shell debug: http://hastebin.com/vuberezuhe.tex

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Sep 28, 2015

But what about my prev comment?

http://conemu.github.io/en/CoProcManager.html

Does that concern you?

@OverlordQ

This comment has been minimized.

OverlordQ commented Sep 28, 2015

I have those files yes, but I never had crashes between 150814 and 150910

@OverlordQ

This comment has been minimized.

OverlordQ commented Sep 28, 2015

Renaming the folders fixes the ConEmu issue, but it's still a regression as the 'workaround' in 150910 broke what wasn't previously breaking

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Sep 28, 2015

As docs state I can't fix third-party problems which were reported by several users. You are lucky if there were no crashes on your computer.

@OverlordQ

This comment has been minimized.

OverlordQ commented Sep 28, 2015

I guess i scan stick with 150908 then, and never upgrade.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Sep 28, 2015

Bad decision though...

@OverlordQ

This comment has been minimized.

OverlordQ commented Sep 28, 2015

Yeah, but renaming Coprocmanager removes the ability for the drivers for the nvidia drivers to switch between offloading normal activity to the integrated Intel drivers vs the heavier nvidia gpu.

@bjmiller

This comment has been minimized.

bjmiller commented Oct 4, 2015

To add a little data: I'm having the same basic problem as mentioned here, and in a few other issues. Disabling Inject ComEmuHk makes git work properly for me again.

Is there a way to exclude specific apps from the hook? (Such as git...) That may be a good compromise, since it's been pretty hard for you to debug this, and it only seems to affect certain specific apps run within the terminal.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 5, 2015

Excluding would be worse. If vim starts from (excluded) git, you would have a crash most probably.

Different technique implementation in progress.

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 7, 2015

How about build 151006?

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 22, 2015

Nobody interested...

@Maximus5 Maximus5 closed this Oct 22, 2015

@bjmiller

This comment has been minimized.

bjmiller commented Oct 22, 2015

I haven't had a chance to look at this yet. :)

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Oct 22, 2015

Well, post here when you take a look

@OverlordQ

This comment has been minimized.

OverlordQ commented Oct 22, 2015

Yeah sorry, somehow missed the build message. I'll check tomorrow once I'm back at the afflicted computer.

@OverlordQ

This comment has been minimized.

OverlordQ commented Oct 30, 2015

Looks good here, up through 151029 are working still.

@bjmiller

This comment has been minimized.

bjmiller commented Oct 30, 2015

Looks good. I originally managed to fix problems with git by simply updating git to the current version. Under 151029, I haven't found anything that fails yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment