nemo-terminal: F4 toggle doesn't work when VTE terminal has keyboard focus
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 74/100
Research direction
Start in nemo_terminal.py at _toggle_visible() and inspect how the Nemo window receives F4 while the VTE terminal has focus. Reproduce the listed steps, then evaluate the existing window key handler and the suggested accelerator or terminal-level handling. Done means F4 opens and closes the embedded terminal without requiring focus to move elsewhere.
Written by the indexing model from the issue text.
Description
Steps to reproduce:
- Open Nemo
- Press F4 to open the embedded terminal
- Type something in the terminal (terminal has keyboard focus)
- Press F4 again to close the terminal
Expected: Terminal closes (toggle).
Actual: F4 is consumed by the VTE terminal widget; nothing happens. Must click outside the terminal first to move focus to the file list, then F4 works.
Comparison: Dolphin's embedded terminal (Konsole) handles this correctly — F4 toggles regardless of where the focus is.
Root cause: In nemo_terminal.py:_toggle_visible() (line 572), the key-press-event is connected to the Nemo window with connect_after, but when the VTE terminal widget has focus, it consumes the key event and it never reaches the window handler.
Suggested fix: Either:
- Add F4 as an accelerator on the window (not just a key-press handler), so it works regardless of focus
- Or use a global keybinding that's not consumed by VTE
- Or connect the key handler on the terminal widget itself instead of the window
Tested on Linux Mint 22.3, nemo-terminal 6.6.0.
- Dominant language
- C
- Stars
- 487
- Forks
- 171
- Avg merge
- 10d 19h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/nemo-extensions
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
linuxmint/nemo-extensions#592 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
linuxmint/nemo-extensions#588 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
linuxmint/nemo-extensions#587 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
linuxmint/nemo-extensions#585 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
linuxmint/nemo-extensions#581 · 4 comments ·
All issues in linuxmint/nemo-extensions
Similar issues
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
tmewett/BrogueCE#929 · 1 comment ·
Maintainers usually reply within 1 day
-
bug : find_key() compares kty against "ocy" instead of "oct", breaking kid-less HS256 verificationOpen
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
OpenPrinting/cups#1756 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
SteamGridDB/SGDBoop#147 ·