warpdotdev / warpdotdev/warp

Modify copied blocks so command is clearer (prepend with dollar sign $ and space)

Open
#4,834 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement triaged
Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Description

Describe the solution you'd like?

It would be nice in blocks, shared blocks, copied output, etc, if the command had a $ before it to make it clear that this is a shell command. For example:

w
11:12  up 16 days, 22:25, 1 user, load averages: 1.96 1.72 1.84
USER     TTY      FROM              LOGIN@  IDLE WHAT
samh     console  -                09Apr24 16days -

It's not easy to tell what's going on here. And typically, when devs share instructions or examples of commands and expected output, we identify the command separately from the output, e.g.:

$ w
11:12  up 16 days, 22:25, 1 user, load averages: 1.96 1.72 1.84
USER     TTY      FROM              LOGIN@  IDLE WHAT
samh     console  -                09Apr24 16days -

It would be great to have this show up in blocks this way.

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

No response

Additional context

No response

How important is this feature to you?

2

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

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.

Research direction

The issue names blocks, shared blocks, and copied output but no files or tests. Start by locating the entry points that render or copy these blocks, then reproduce a copied shell command in each named context. Done means the command is consistently distinguishable from its output across those contexts.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.