@bpasero Hi, I have two questions:
Do we need to make settings for this obstacle?
If I add judgment for pinned here, the scope may be a little larger. Do we need to move the judgment to where the mouse middle button is clicked to determine, in order to reduce the impact scope of this obstacle?
Thanks!

@weartist I would have a setting which then we can turn on by default to see how many users are upset. If there are no complaints I am also easy to remove the setting again and make it the default behaviour.

I would think the change should only be where we close from mouse middle click:

For the "Open Editors" view:

For tabs:

For no tabs:

@weartist I would have a setting which then we can turn on by default to see how many users are upset. If there are no complaints I am also easy to remove the setting again and make it the default behaviour.

I would think the change should only be where we close from mouse middle click:

For the "Open Editors" view:

vscode/src/vs/workbench/contrib/files/browser/views/openEditorsView.ts

Line 271 in 5e0c49c

e.element.group.closeEditor(e.element.editor, { preserveFocus: true });

For tabs:

vscode/src/vs/workbench/browser/parts/editor/tabsTitleControl.ts

Line 891 in 5e0c49c

this.closeEditorAction.run({ groupId: this.group.id, editorIndex: index });

For no tabs:

vscode/src/vs/workbench/browser/parts/editor/noTabsTitleControl.ts

Line 108 in 5e0c49c

this.group.closeEditor(this.group.activeEditor);

Understand, i rushed XD, and thank you for the code point!

I simply completed the feature and tested it, hoping it worked fine @bpasero

The method is actually called isSticky in the internal API, I know its misleading, but isPinned is for a different feature (preview tabs).

Should the setting be more specific to mention that it is for mouse middle click only? We already prevent closing a tab by keybinding irrespective of the setting.

That is, can I replace isPinned with isSticky? I did confuse the two judgments a bit, I found that the two were almost identical, then I found their implementation, but still not possible to confirm whether they are equal haha

isPinned:

and I'll go and change the description again

Yes, can be replaced with isSticky.

@weartist I had a thought: what if the setting changes back to the original name you had in mind and becomes an enumeration that allows to fully control the behaviour for closing:

• one option to never close for neither keyboard nor mouse
• one option to never close for keyboard
• one option to never close for mouse
• one option to always allow to close

This would be a good way to keep the setting around even for the future to let people fully control the close behaviour and then we can think about a reasonable default?

@weartist I had a thought: what if the setting changes back to the original name you had in mind and becomes an enumeration that allows to fully control the behaviour for closing:

• one option to never close for neither keyboard nor mouse
• one option to never close for keyboard
• one option to never close for mouse
• one option to always allow to close

This would be a good way to keep the setting around even for the future to let people fully control the close behaviour and then we can think about a reasonable default?

@bpasero Does your mention of ' never close for mouse' include right-clicking the tab and selecting 'close' from the pop-up menu? I think it's well that this feature can be fully controlled through settings. For me, I need to prevent the keyboard from closing tabs, but I still want to be able to close them by right-clicking with the mouse, otherwise I'd have to cancel pinned and click again every time.

Yeah I was suggesting to target only these 2 cases:

• closing by keybinding
• closing by mouse

But not other actions, such as the menu.

In this case, does mouse closing only include clicking the mouse middle button? I will try to write a simple version.

will start tomorrow. Tonight I will think about whether there are some other cases to consider XD

Yeah, so I meant middle-mouse-click.

@bpasero I want to abstract the logic that judges whether to block closing into a method, something like 'isPinned', but I didn't find a good place for it. The current code has some repetition and verbosity

have reworked the relevant code, but have not tested it yet

After a simple test, the function looks fine

@weartist I did a review and pushed changes, can you please test out everything works as expected?

@weartist I did a review and pushed changes, can you please test out everything works as expected?

sure, thanks! I'll start testing after reading it, this is my favorite part to learn in order for me to improve haha

@bpasero It's run as excepted