sandr01d

I do like this functionality and think it would be a great addition. That being said, I think we should stick to the obvious git commands for each scenario and...

> @cjappl Great to hear that you like it. :-) > > Yes, you are right, it will be a new kind of feature for forgit. Again some thoughts on...

FYI: I removed the empty line at 120 that did not make sense anymore. Everything else is exactly as it is in #326.

@carlfriedrich > One thing to improve, though: I would like to see the PR description in the commit message. Furthermore it should have a "Refactor: " prefix or something similar...

FYI: I will keep changes as commits around here to make the review process easier, but will squash everything from this PR together when I rebase #326.

> I imagine in the end we'll have something like this: > > PR 1 (this one) contains commit A > PR 2 contains commits A & B > PR...

@cjappl I've implemented the changes you requested, do you approve aswell?

Changes have been merged with #326

Git escapes paths by default, leading to the described behavior. You can disable this with `git config core.quotePath false`. Afterwards you should be able to work with the file you...

It does not appear to be a super easy fix, but seems doable. I'll leave this issue open and will take a closer look once I find the time if...