Skip to content
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

Add "Open in Opposite Group" Feature to Improve Editor Navigation #336

Closed
sfyr111 opened this issue Mar 21, 2024 · 1 comment · Fixed by #337
Closed

Add "Open in Opposite Group" Feature to Improve Editor Navigation #336

sfyr111 opened this issue Mar 21, 2024 · 1 comment · Fixed by #337
Assignees
Milestone

Comments

@sfyr111
Copy link

sfyr111 commented Mar 21, 2024

Description

The "Open in Opposite Group" feature allows users to quickly open the currently active editor tab in the opposite editor group, which can significantly enhance navigation efficiency when working with multiple files. This feature aims to mimic the convenience found in IntelliJ IDEA, providing a similar user experience for VSCode users.

Expected Behavior

  • When triggered, the currently active file should open in the opposite editor group. If the file is in the first group, it should open in the second, and vice versa.
  • The focus should move to the newly opened editor tab, allowing immediate interaction.
  • Triggering the command again should toggle the view back to the original editor group, maintaining focus on the file.

Current Behavior

  • Currently, VSCode does not offer a built-in command to quickly toggle the active editor between groups while maintaining focus.

Possible Solution

  • Implement a new command intellij.openInOppositeGroup that handles the opening of the active editor in the opposite group and manages focus accordingly.

This feature would be a valuable addition for users who frequently work with multiple files and editor groups, enhancing their workflow and productivity.

sfyr111 added a commit to sfyr111/vscode-intellij-idea-keybindings that referenced this issue Mar 21, 2024
@kasecato kasecato self-assigned this Mar 23, 2024
@kasecato kasecato added this to the v1.6.1 milestone Mar 23, 2024
@kasecato
Copy link
Owner

kasecato commented Apr 1, 2024

@sfyr111 I just released it as v1.6.1

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

Successfully merging a pull request may close this issue.

2 participants