Posted in Uncategorized

“Multi Cursor on Click” seems to always be disabled in Atom 1.48.0

   September 16, 2020  9 Comments on “Multi Cursor on Click” seems to always be disabled in Atom 1.48.0

Prerequisites

Description

Multiple cursors on click don’t seem to work now – this is regardless of whether “Multi Cursor on Click” is checked or not in the Editor panel. Disabling it in the settings does add the key to config.cson, but explicitly setting it to true in the config file does not work either.

Steps to Reproduce

  1. Open a file
  2. Hold Ctrl and click multiple locations in the file

Expected behavior:

Multiple cursors to be active at each location that is clicked.

Actual behavior:

The cursor moves to the last location that is clicked.

Reproduces how often:

100%%

Versions

Atom    : 1.48.0
Electron: 5.0.13
Chrome  : 73.0.3683.121
Node    : 12.0.0

apm  2.5.0
npm  6.14.5
node 10.20.1 ia32
atom 1.48.0
python 2.7.10
git 2.18.0.windows.1
visual studio 2015

Windows 10

Additional Information

I know this can arise due to an interaction with hyperclick, but that should not be the case here as I have my hyperclick configured to use another key combination. Also I did check that it occurs in safe mode.

Full dicussion on github.com

9 thoughts on ““Multi Cursor on Click” seems to always be disabled in Atom 1.48.0”

  1. @HugoMcPhee posted and deleted a comment linking to #20804 which does indeed seem to offer a fix for this 😄

    As a workaround I added

    editor:
  multiCursorOnClick: true

    under core in my config.cson which resolves it for now, so thanks for that! 👍

  4. @HugoMcPhee posted and deleted a comment linking to #20804 which does indeed seem to offer a fix for this smile
    As a workaround I added

    editor:
  multiCursorOnClick: true

    under core in my config.cson which resolves it for now, so thanks for that! +1

    This workaround doesn’t work for me…

    At first, it was a bit misleading, but the key is to add the workaround under core. So in the end, I set it like that and it worked:

    "*":
  core:
    editor:
      multiCursorOnClick: true

  5. QA on Atom is getting rougher and rougher, this was reported nearly three weeks ago during the beta. The last release broke several prominent plugins and this release has broken one of the editors’ key features.

    The fix above works on all platforms, just ensure you find the appropriate place to insert the config lines (you probably have core already, you may have editor).

  6. If you add multiCursorOnClick: true under

    "*":
  editor:

    This WILL NOT WORK. You need to add it under:

    "*":
  core:
    editor:
        multiCursorOnClick: true

    Which, for me, required adding a new editor: section under core:

  7. If you add multiCursorOnClick: true under

    "*":
  editor:

    This WILL NOT WORK. You need to add it under:

    "*":
  core:
    editor:
        multiCursorOnClick: true

    This worked for me, but make sure you add it right under core: if you have other lines put them after multiCursorOnClick: true

  9. I noticed something weird in my config.cson. Its beginning looked like this after an update:

    "*"
    "*"
        "atom-material-ui": ...
        "autoclose-html": ...
        more plugins...
    "atom-material-ui": ...
    "autoclose-html": ...
    more plugins...

    The “*” property included the same property again and the whole tree of configurations with it. So i deleted this nested branch, then added multiCursorOnClick: true to “*”.core.editor, as multiple people mentioned here, and it works

    Atom 1.48.0, windows 10 build 1909