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

Deleting Notebooks on click of delete Keyboard Key #10675

Closed
harsh-791 opened this issue Jul 3, 2024 · 3 comments
Closed

Deleting Notebooks on click of delete Keyboard Key #10675

harsh-791 opened this issue Jul 3, 2024 · 3 comments

Comments

@harsh-791
Copy link

Operating system

Linux

Joplin version

3.0.12

Desktop version info

Joplin 3.0.12 (dev, linux)

Client ID: d6d921f8d92745daa99f74e8c5cddb1b
Sync Version: 3
Profile Version: 47
Keychain Supported: No

Revision: 6215de6 (dev)

Backup: 1.4.1

Current behaviour

If i have selected a particular noteboook, then i doesn't get deleted on click of delete keyboard button

Steps to Reproduce:

Open joplin.
Select a notebook you wish to delete.
Press the delete keyboard key.

Actual Result:

The notebook is not deleted. Users must double-click the notebook and then select the "Delete Notebook" option from the context menu to delete it.
Screenshot from 2024-06-28 20-20-23

Expected behaviour

Desired Functionality:

Please add support for using the delete keyboard key to delete selected notebooks. This enhancement will improve user efficiency and align with common user expectations for deleting files or items in many applications.

Logs

No response

@harsh-791 harsh-791 added the bug It's a bug label Jul 3, 2024
@shubhiscoding
Copy link

@laurent22 please assign this to me

@harsh-791
Copy link
Author

harsh-791 commented Jul 3, 2024

@laurent22 i wish to resolve the issue

@Daeraxa
Copy link
Collaborator

Daeraxa commented Jul 3, 2024

  1. This is a feature request rather than a bug and therefore needs to be discussed on the forum (unless you are indicating this is a regression in which case which version showed the correct behaviour last?).
  2. We do not assign issues

@Daeraxa Daeraxa closed this as not planned Won't fix, can't repro, duplicate, stale Jul 3, 2024
@Daeraxa Daeraxa removed the bug It's a bug label Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants