Uploaded image for project: 'MongoDB Shell'
  1. MongoDB Shell
  2. MONGOSH-954

modifier + arrow keys do not work in mongosh

    • Type: Icon: Bug Bug
    • Resolution: Won't Do
    • Priority: Icon: Minor - P4 Minor - P4
    • No version
    • Affects Version/s: 1.0.4
    • Component/s: Embedded Shell
    • None
    • Not Needed

      Problem Statement/Rationale

      In the new mongosh shell, option + arrow keys don't work (this is on a mac, latest os) starting up the legacy mongo shell, the option keys work as expected

      In mongosh, option + arrow just acts like a normal arrow key

      Steps to Reproduce

      I am accessing the mongo shell by typing mongosh. I type some code say. db.users.insert().   If I want to navigate around those words, in the legacy shell I can use option + left-arrow to go backward a word. However in mongosh, it only goes back one space ignoring the option key. https://docs.mongodb.com/manual/reference/mongo-shell/

      Expected Results

      The expected behavior is for option +left-arrow to go back a word instead of a space as it does in the legacy shell and explains in the documentation.

      Actual Results

      In the new mongosh shell, option + arrow keys don't work

      Additional Notes

      I have the latest version of mongo docker https://hub.docker.com/_/mongo?tab=tags  v5.0.2 which runs mongosh v1.0.4. (I also have v5 run directonly on my machine which has mongosh v1.0.3)

      I have mongo installed natively on my laptop. I also have it as a docker container. Running mongosh on the latest macOS has this issue. Running mongosh in docker also has this problem.

      In the native mongo shell, the option keys work in both the native OS and the docker container

        1. Sep-17-2021 08-52-33.mp4
          23.50 MB
          Massimiliano Marcon

            Assignee:
            Unassigned Unassigned
            Reporter:
            qhenkart@gmail.com Quest Henkart
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: