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

Keep the file browser in the same directory when deleting a file or subdirectory #108463

Closed
Pomax opened this issue Oct 10, 2020 · 2 comments
Closed
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@Pomax
Copy link

Pomax commented Oct 10, 2020

Currently, deleting a file in the file browser sidebar will cause the file browser to immediately jump to whatever the currently open file is, instead of staying in the same directory, making it really hard to do some basic file management.

Instead, the file browser should just move focus to whichever dir owns the file/dir that got deleted:

┬ root
│ ├ some dir  <─ highlight this...
│ │  ├ some file
┆ ┆  └ some other file <─ ...when deleting this

And then don't change the file browser location until the user explicitly focuses on an open file again (e.g not on scroll, as scrolling does not imply working on a file in the slightest; it's a consultation at best, which might in fact guide which other files need deleting).

@Pomax Pomax changed the title Keep the file browser in the same directory when deleting a file Keep the file browser in the same directory when deleting a file or subdirectory Oct 10, 2020
@isidorn
Copy link
Contributor

isidorn commented Oct 20, 2020

Closing as dup of #71315

@isidorn isidorn closed this as completed Oct 20, 2020
@isidorn isidorn added the *duplicate Issue identified as a duplicate of another issue(s) label Oct 20, 2020
@Pomax
Copy link
Author

Pomax commented Oct 20, 2020

@isidorn that sounds like it's related, but also rather different given the initial description?

@github-actions github-actions bot locked and limited conversation to collaborators Dec 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants