Skip to content

Destructive behaviors shouldn't be unconfigurable: add configuration to "tab close with middle click" #42606

@eugenesvk

Description

@eugenesvk

Summary

Desctructive actions should always be configurable, even less critical ones like closing a tab on (middle) mouse click

Description

A recent update added an unconditional destructive action to close a tab on middle mouse click #41628.
But similar to the "cross" close icon, it breaks the potential to enable nondestructive mouse interaction in Zed (you can disable the "close" icon) - e.g., when you scroll the tab bar and accidentally middle-click the tab is closed.

DESCRIPTION_HERE

Steps to reproduce:
N/a, the bug is in the new breaking behavior without a fallback

Expected Behavior:
Ability to disable tab close on mouse middle click

Actual Behavior:
It's always on

Zed Version and System Specs

Zed: v0.213.0 (Zed Dev 2bcfc12)
OS: Windows 10.0.26100
Memory: 12 GiB
Architecture: x86_64
GPU: NVIDIA GeForce GTX 750 || NVIDIA Corporation || 576.2 r575_92

If applicable, attach your Zed.log file to this issue.

Zed.log

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions