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

keybindings to "find" next/previous occurences not working ? #15736

Open
1 of 2 tasks
vimchun opened this issue May 31, 2024 · 0 comments
Open
1 of 2 tasks

keybindings to "find" next/previous occurences not working ? #15736

vimchun opened this issue May 31, 2024 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@vimchun
Copy link

vimchun commented May 31, 2024

Applies To

  • Notebooks (.ipynb files)
  • Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

Hi, I can use my keybindings on a classic file (ie a python file) to find the next/previous occurence of the string defined on the find widget (the one appearing on the top right inputbox). That's working well using :

    { "key": "ctrl+n", "command": "editor.action.nextMatchFindAction"},
    { "key": "ctrl+p", "command": "editor.action.previousMatchFindAction"},

Therefore, it does not seem working on a notebook file. I can see with the "Keyboard Shortcuts Troubleshooting", that these commands are well triggered, but I cannot see the next/previous occurence focused.

Are these commands supposed to work on notebooks ?
If not, which commands should I use ?

Thanks in advance, I am trying to have a config where I use the mouse as least possible.

VS Code Version

1.89.1

Jupyter Extension Version

v2024.4.0

Jupyter logs

No response

Coding Language and Runtime Version

No response

Language Extension Version (if applicable)

No response

Anaconda Version (if applicable)

No response

Running Jupyter locally or remotely?

None

@vimchun vimchun added the bug Issue identified by VS Code Team member as probable bug label May 31, 2024
@VSCodeTriageBot VSCodeTriageBot added the triage-needed Issue needs to be triaged label Jun 1, 2024
@amunger amunger assigned Yoyokrazy and unassigned amunger Jun 3, 2024
@amunger amunger removed the triage-needed Issue needs to be triaged label Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

4 participants