# sublime: Don't map editor::FindNextMatch by default \(\#31029\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/89700c3682db98cab494b9d481d0856d63a7ad47)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 89700c3682db98cab494b9d481d0856d63a7ad47

Requested commit: 89700c3682db98cab494b9d481d0856d63a7ad47

Commit: 89700c3682db98cab494b9d481d0856d63a7ad47

Tree: 48b5452257b6a7da46927f21f7cebbb1710523cc

Author: Peter Tripp

Committer: GitHub

## Message

````
sublime: Don't map editor::FindNextMatch by default (#31029)

Closes: https://github.com/zed-industries/zed/issues/29535

Broken in: https://github.com/zed-industries/zed/pull/28559/files

Removes `editor::FindNextMatch` and `editor::FindPreviousMatch` from the
default sublime mappings. If you would like to use this, you will have
to add them to your user keymap. Reverts the previous behavior where
cmd-g / cmd-shift-g relies on the base keymap.

Linux:
```json
  {
    "context": "Editor && mode == full",
    "bindings": {
      "f3": "editor::FindNextMatch",
      "shift-f3": "editor::FindPreviousMatch"
    }
  }
```

MacOS:
```json
  {
    "context": "Editor && mode == full",
    "bindings": {
      "cmd-g": "editor::FindNextMatch",
      "cmd-shift-g": "editor::FindPreviousMatch"
    }
  },
```


Release Notes:

- Fixed a regression in Sublime Text keymap for find next/previous in
the search bar
````

## Parents

- [76094022004ddb151576a10f20723f2cdd18463d](https://git.cafe/gitcafe/zed/commit/76094022004ddb151576a10f20723f2cdd18463d?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/89700c3682db98cab494b9d481d0856d63a7ad47?format=markdown)