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

editor.multicursorModifier: cmd should be the default #27503

Closed
bpasero opened this issue May 30, 2017 · 10 comments
Closed

editor.multicursorModifier: cmd should be the default #27503

bpasero opened this issue May 30, 2017 · 10 comments
Assignees
Labels
under-discussion Issue is under discussion for relevance, priority, approach
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented May 30, 2017

Testing #27480

We should change our default to editor.multicursorModifier: cmd to follow what other editors do.

@alexdima
Copy link
Member

I leave this up to @seanmcbreen who can drive it, same as with the other default options changes. I agree, if we ever want to change the default this milestone is the best one, as we are tweaking other defaults and we can communicate the changes all at once.

@alexdima alexdima assigned seanmcbreen and unassigned alexdima May 30, 2017
@isidorn
Copy link
Contributor

isidorn commented May 30, 2017

Agree with @bpasero here, we were a bit too passionate about cmd + click to go to defintion when we made the original decision.
However if we make the default switch we need to think how to notify the users how are used to the old cmd + click behavior.
If we decide not to make the switch then we should make this setting more discvoerable #27551

@bpasero
Copy link
Member Author

bpasero commented May 30, 2017

  • @Microsoft/vscode for input

@seanmcbreen
Copy link

I've been mulling this over all day and I think we should change the default to match the other editors.

We will get some push-back on this for people who have developed muscle memory, so we will need to clearly document it (along with the other changes). The thing that pushed me over the line was the realization that many, many more people will work with cursors vs goto definition.

We had discussed making this a change only for people with the Sublime [Keymap] extension installed - but changing the setting on update and filtering to just the group seams not great either.

We have a few days to close but I vote for changing the default.
Sean

cc @egamma @waderyan

@bpasero bpasero added this to the May 2017 milestone May 31, 2017
@bpasero bpasero added under-discussion Issue is under discussion for relevance, priority, approach editor labels May 31, 2017
@Tyriar
Copy link
Member

Tyriar commented May 31, 2017

To clarify, this only affects Mac right? Won't it feel weird that it's alt on Windows and cmd on Mac for people who use both?

The thing that pushed me over the line was the realization that many, many more people will work with cursors vs goto definition.

@seanmcbreen is this just speculation?

@Tyriar
Copy link
Member

Tyriar commented May 31, 2017

Also remember that alt is taken by the OS on Linux so if the switch happens to ctrlCmd (#27680), that means that go to definition via alt+click will be unusable on the majority of Linux machines.

@egamma
Copy link
Member

egamma commented May 31, 2017

@seanmcbreen traditional IDEs like Eclipse, Intellij, Webstorm, Netbeans are all using cmd+click for go to definition, this is why @bpasero picked it (but he has forgotten by now 😄), IDE converts used to this feature will be surprised.

I like the suggestion in #27551 to make this setting more discoverable and would favor this solution over changing the default.

@seanmcbreen
Copy link

OK full circle - I've chatted to more people, seen the comments here, played with it a little and I think we may want to slow ourselves down a tiny bit :)

I propose:

  1. We clearly document the new setting (it's impact on box selection, it's impact of multi cursor, it's impact on follow hyper link and any other side effects)
  2. Feature this very clearly in the Docs, Release Notes, Sublime Blog post and Keymap extension
  3. Place a toggle in the Selection menu for enabling this - I propose:
    Use Ctrl Click for Multi-cursor and Use Alt Click for Multi-cursor
    Make this it's own section at the bottom (less convicted on where it is just trying to propose something)
  4. Add this to the most common settings in the settings editor

We will then listen to feedback and learn more about how users react. The we can include in the next wave of settings thinking. We don;t need to change everything at once. I'm really glad we have this now but we don;t need to go all in on day 1.

@egamma - assuming this works for you and the rest of the team can you cover item 3 and 4. I'll get the other parts covered off.

Sean

@alexdima
Copy link
Member

alexdima commented Jun 1, 2017

@seanmcbreen
point 3 => #27551
point 4 => #27811

@aeschli aeschli closed this as completed Jun 2, 2017
@aeschli aeschli reopened this Jun 2, 2017
@aeschli aeschli closed this as completed Jun 2, 2017
@alejandromagnorsky
Copy link

alejandromagnorsky commented Jun 16, 2017

I was wondering if you can also include the ability to enable multi-cursor by pressing the middle click. That's how I normally use this feature in Sublime. Thanks.

EDIT: I actually found this ticket where it asks the same thing:
#28186

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

8 participants