Replies: 2 comments
-
I'm replying to a post several months old so I'm not really expecting a response. Having said that, here is a quick video of a proof-of-concept that kind of does what you have described. I stress that it is only a proof-of-concept right now. Several system calls are used for each entry and that will most likely make things rather slow on some systems. Currently only a couple of functions have been tested - opening files and toggling inline diff. Now some potential issues:
If you are still interested I'll continue working on this (will probably take another couple of weeks) and post a diff patch against the master. |
Beta Was this translation helpful? Give feedback.
-
Actually, I don't recommend doing this. You quickly end up with a very confusing set of paths such as this example: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there! I wanted to ask if there's a solution to the following issue I sometimes face when working with large monorepos using Fugitive
Before using Fugitive, I would use the plain command line or an IDE viewer when working with git. In those cases, "git status" would show me the changed files relative to my current working directory. However, when using the
:Git<CR>
command in Fugitive to view the summary, the paths are shown relative to the root of the git repository, which can cause problems when using it in vertical splits (paths are too long)Is there a way to make Fugitive prefer the current working directory relative paths when displaying the summary?
Beta Was this translation helpful? Give feedback.
All reactions