Terminal Data Entry And Keyboard UI/UX improvements

Open
#1,744 14 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
cli, desktop

Research direction

No files, tests, or entry points are named. Start by locating the terminal command-entry, output-selection, and focus-handling code; done means supporting the requested larger or adjustable entry area and reliably returning focus to command input after navigation or the application regains focus.

Written by the indexing model from the issue text.

Description

area:settings-keybindings enhancement triaged
Discord username (optional)

No response

Describe the solution you'd like?
Here's the basic issue with this terminal that is super annoying compared to any standard terminal and it can be improved so easily in your source code.

There is such a small hit box to land inside your terminal space to enter in new commands.  Make it so you can drag an adorner of some kind and configure and stretch the height of the entry of where you enter your commands.  Its hard to get your mouse in a hit box of 75 pixels so I can run my next command.  This would improve area height to click and users can scroll higher to see more output of previous commands

You have to remember that every terminal always is ready to accept the next command, but yours is different with the output grouping and as you are interacting with it and ALT-TABing with a mouse, you most likely will select the output which is a problem (most people dont care about copying the output of the last command, they are trying to send another command).  So I would say that after the application is out of focus, always focus the caret into the command execution 75pixel area so they can just type and not have to move the mouse down to the small hit box to actually run a command.  So even if an output was previously selected, unselect it and focus on the entry of a new terminal command.

I shouldnt have to write scripts against your terminal to make the user experience better, this needs to be done ASAP.

Next, for output of each command above there, Its neat how you can use the up arrow to select commands to either copy the command and its output, but the problem with this is when you hit the bottom of the stack and you are pressing down key, it should focus the area of your command so you can enter another command easily.

With these simple UX improvements my workflow will be vastly improved and I my hatred of using it when these problems arise will begin to wane.
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

No response

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.