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

Add ability to disable blocks entirely #3227

Closed
x48115 opened this issue Jun 21, 2023 · 1 comment
Closed

Add ability to disable blocks entirely #3227

x48115 opened this issue Jun 21, 2023 · 1 comment
Labels
Feature requests Feature Requests

Comments

@x48115
Copy link

x48115 commented Jun 21, 2023

Discord username (optional)

No response

Describe the solution you'd like?

Expected results: Click anywhere in a pane to active command input.
Actual results: If a pane I clicked on is already active a block is selected instead.

My use case:
I am often context switching between warp and other apps. I don't always remember what pane was active last. To make sure, when I command tab back to warp I click the pane I want to work in. If the pane is already active though a block is selected. In order to actually get to the text input I either need to double click the block again or press tab which is an annoyance because this happens all the time/constantly.

I have no use case for blocks. All I want is a simple pane that shows all historical results. To me blocks over-complicate terminal (I already have tabs and panes, why do I need another subdivider?) and I would prefer an option to disable them completely. Blocks don't make things easier for me, they crowd the UI and I prefer something more simple.

Is your feature request related to a problem? Please describe.

No response

Additional context

No response

How important is this feature to you?

5 (Can't work without it!)

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

None

@x48115 x48115 added the Feature requests Feature Requests label Jun 21, 2023
@dannyneira
Copy link
Member

Thanks for submitting this @x48115 At this time there is no intention to disable Blocks as it's an integral part of Warp and would require significant refactoring of the codebase. Regarding your pain point of having to click on the input twice there a request tracking this over at #739 it's being worked on and should be fixed in an upcoming build.

As a workaround, you can also click on Warp and press CMD-L to quickly jump to the [input editor](CMD-L to quickly jump to the input editor).

We'll be closing this as a duplicate of the foregrounding issue and there is no intention to disable Blocks in the near future.

@dannyneira dannyneira closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature requests Feature Requests
Projects
None yet
Development

No branches or pull requests

2 participants