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
Goto Definition does not reuse tabs in other groups #121
Comments
This issue is a bit tricky. I also noticed this, but I thought about whether I would normally want to open the definition in an open view or in its own view. Usually it would be the 'own view'. However, currently ST does neither because it will focus and scroll existing views iff they are in the same group as the quick panel. Imo it could be done that shift+enter would always open the definition in a new view while normal enter would focus and scroll the existing view, regardless of group position. |
Which package controls this behaviour? |
The Default package. Refer to |
Would really appreciate this feature. For instance referencing the same file multiple times opens too many tabs. |
I know we're not big fans of "me too" style comments, but I would appreciate a feature that disabled the current way this works and reuses open editors already. My standard workflow is 1/3rd terminal, 2/3 ST3 with two panes, prod code in the first and test code in the second. It's frustrating to goto defintion in a test and have it not jump to the already open code editor in the prod code pane. |
This issue has been moved back to the other repo. |
From @jimlawton on April 20, 2015 13:10
I use a 2-group setup, generally with library code in the right-hand group. Previously, "Goto Definition" would jump to the implementation in the other group if I already had a tab for the module there, or otherwise open a new tab in the current group.
Now, however, (and for the last month or more), "Goto Definition" always opens the destination in a new tab in the current group.
Steps to reproduce:
Expected result: the cursor jumps to the function definition in Group 1.
Actual result: the cursor jumps to the function definition in a new tab in Group 2.
Details:
Copied from original issue: sublimehq/sublime_text#813
The text was updated successfully, but these errors were encountered: