gdh1995
Any parameter to tune the longest duration of visitPreviousTab?
The current duration time is too short that before I can determine whether to stay or leave, Vimium-C will have taken this tab to be one of the tabs to switch between.
Up to now there's no option to do so. There's another plan to add "memory" mode to visitPreviousTab, which means a second triggering will jump to the 2nd-recent tab, until any tab switching from other sources happens. How do you think about it?
---Original--- From: @.> Date: Tue, Aug 24, 2021 19:07 PM To: @.>; Cc: @.***>; Subject: [gdh1995/vimium-c] Any parameter to tune the longest duration of visitPreviousTab? (#414)
The current duration time is too short that before I can determine whether to stay or leave, Vimium-C will have taken this tab to be one of the tabs to switch between.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
The max length of the recent-tab queue and the duration time are two good but disparate dimensions for improvement of the user experience. I suggest you also schedule my proposal to your plan.
But you may press 2xxx to jump to the second recent tab now.
---Original--- From: @.> Date: Tue, Aug 24, 2021 21:36 PM To: @.>; Cc: "Dahan @.@.>; Subject: Re: [gdh1995/vimium-c] Any parameter to tune the longest duration of visitPreviousTab? (#414)
The max length of the recent-tab queue and the duration time are two good but disparate dimensions for improvement of the user experience. I suggest you also schedule my proposal to your plan.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.