You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really nice to have to option to specify a pane to not receive input from tab-syncing at all.
This is useful when you have long running cli-tools (e.g. bottom/htop, a file-manager etc.) and you want to avoid receiving input from a synced tab, so that nothing gets messed up.
Currently harmful things could happen. Hypothetical example: lets say I have multiple panes open and one is running ranger.
When I now tab-sync and cd into a directory and its name contains dd I might accidentally delete files.
This is especially "evil" with stacked panes, as they make it more likely that one forgets or overlooks which applications they are currently running.
While having a layout option would not completely solve the issue it would at least give the ability to be 100% sure that certain panes won't receive input, so that one could use these to run long running applications.
The text was updated successfully, but these errors were encountered:
It would be really nice to have to option to specify a pane to not receive input from tab-syncing at all.
This is useful when you have long running cli-tools (e.g. bottom/htop, a file-manager etc.) and you want to avoid receiving input from a synced tab, so that nothing gets messed up.
Currently harmful things could happen. Hypothetical example: lets say I have multiple panes open and one is running ranger.
When I now tab-sync and cd into a directory and its name contains
dd
I might accidentally delete files.This is especially "evil" with stacked panes, as they make it more likely that one forgets or overlooks which applications they are currently running.
While having a layout option would not completely solve the issue it would at least give the ability to be 100% sure that certain panes won't receive input, so that one could use these to run long running applications.
The text was updated successfully, but these errors were encountered: