You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
Opening a file from cmd-b or cmd-p should go directly to the file if it's already opened, regardless of pane.
Behavior observed
The file is selected if you're in the same pane, but opened new if not.
Thoughts
This could be behavior that can be had both ways. For example, if you open a file with enter it will go to the already opened file but if you open with shift-enter it opens a new copy in the current pane.
The text was updated successfully, but these errors were encountered:
This used to be the default behavior and people really didn't like it, so if we add this I'd say shift-enter should be bound to this option by default. Then people that prefer it to be bound to enter can change their bindings.
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!
lockbot
locked as resolved and limited conversation to collaborators
Jan 26, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Atom Version
0.43.0
Behavior expected
Opening a file from cmd-b or cmd-p should go directly to the file if it's already opened, regardless of pane.
Behavior observed
The file is selected if you're in the same pane, but opened new if not.
Thoughts
This could be behavior that can be had both ways. For example, if you open a file with enter it will go to the already opened file but if you open with shift-enter it opens a new copy in the current pane.
The text was updated successfully, but these errors were encountered: