Skip to content

Ctrl+W/cmd+w should close current tab - not last tab #12931

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.

Sign up for GitHub

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

Jump to bottom
Closed
2 tasks done
Siedlerchr opened this issue Apr 13, 2025 · 4 comments
Closed
2 tasks done

Ctrl+W/cmd+w should close current tab - not last tab #12931

Siedlerchr opened this issue Apr 13, 2025 · 4 comments
Labels
component: keybinding good first issue An issue intended for project-newcomers. Varies in difficulty.

Comments

@Siedlerchr
Copy link
Member

JabRef version

6.0-alpha

Operating system

Windows

Details on version and operating system

macos/windows

Checked with the latest development build (copy version output from About dialog)

  • I made a backup of my libraries before testing the latest development version.
  • I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

  1. Open multiple libraries
  2. Press ctrl + w (on mac cmd +w )
  3. Notice that the library to the right is closed, not the current selected one

On mac sometimes the command cmd + w does not work at all

Appendix

...

Log File 
Paste an excerpt of your log file here
@Siedlerchr Siedlerchr added the good first issue An issue intended for project-newcomers. Varies in difficulty. label Apr 13, 2025
@github-project-automation github-project-automation bot moved this to Free to take in Good First Issues Apr 13, 2025
@MaywarDeChamplain
Copy link

/assign-me

@github-actions github-actions bot added the 📍 Assigned Assigned by assign-issue-action (or manually assigned) label Apr 14, 2025
@github-actions GitHub Actions
Copy link
Contributor

👋 Hey @MaywarDeChamplain, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

In case you encounter failing tests during development, please check our developer FAQs!

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

Happy coding! 🚀

@koppor koppor moved this from Free to take to Assigned in Good First Issues Apr 14, 2025
@priyanshu16095
Copy link
Contributor

It also exists at, #12530

@MaywarDeChamplain MaywarDeChamplain mentioned this issue Apr 15, 2025
Closed
7 tasks
@koppor koppor moved this from Assigned to In Progress in Good First Issues Apr 15, 2025
@koppor koppor closed this as completed Apr 17, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in Good First Issues Apr 17, 2025
@koppor
Copy link
Member

koppor commented Apr 17, 2025

We did a batch transfer of internal issues. When posting an internal issue of November last year, we did not check if it was posted by a user afterwards. Thank you for the link @priyanshu16095 - closed as duplicate to avoid confusion.

@github-actions github-actions bot removed 📍 Assigned Assigned by assign-issue-action (or manually assigned) 📌 Pinned labels May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: keybinding good first issue An issue intended for project-newcomers. Varies in difficulty.
Projects
Good First Issues
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Force focus on current tab MaywarDeChamplain/jabref
4 participants
@Siedlerchr @koppor @priyanshu16095 @MaywarDeChamplain