Closed vbjay closed 3 years ago
The request wording allows quite a bit of room for various interpretations. Could you please provide clarity and, maybe, visualise what is that you wish.
I think the idea is he wants this feature
in GE.
So I right click on .proj or *.sln files and pick browse to folder. Explorer opens folder that contains that file. I say why not do this with all files and folders in file tree and diff tab.
We already have it
[image: Inline images 1]
Or am I missing something?
On 29 December 2017 at 03:51, Jay Asbury notifications@github.com wrote:
I think the idea is he wants this feature [image: image] https://user-images.githubusercontent.com/3629489/34417186-2442d1dc-ebc5-11e7-9ba3-1c132ec3b8cc.png in GE.
So I right click on .proj or *.sln files and pick browse to folder. Explorer opens folder that contains that file. I say why not do this with all files and folders in file tree and diff tab.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/gitextensions/gitextensions/issues/3620#issuecomment-354319023, or mute the thread https://github.com/notifications/unsubscribe-auth/AEMyXsYeLX_SAAw6Eh9AC5yrOxwYh7iqks5tE8cqgaJpZM4MvNT_ .
I think we have this already, as per @RussKie comment, and me checking that:
File explorer toolbar item exists
In Diff view, we have this option.
File tree
Closing this.
I believe this is a VS/VSIX related query.
Do you want to request a feature or report a bug? feature What is the current behavior? No option to browse the solution's folder, or selected project's folder in GE. If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
What is the expected behavior? Be able to browse to solution/project folders in GE by right clicking the project or solution node in solution explorer. Also add dropdown to browse button in toolbar to be able to select current project, or solution options.
Which versions of GIT and which versions of Windows are affected by this issue? Did this work in previous versions of our tool? N/A