SETTINGS: More finesse in the choice of using a custom PS1 (when ssh distant server)

Open
#1,901 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the existing global custom PS1 setting and the SSH session behavior described in the issue. Define how enabling the prompt for selected remote servers should work, including the server-listing option, and confirm completion by verifying local and remote sessions use the intended prompt behavior.

Written by the indexing model from the issue text.

Description

area:shell-terminal area:ssh enhancement triaged
Discord username (optional)

No response

Describe the solution you'd like?
# Description of my issue
The use on a local PC is exceptional, on the other hand I regularly need to connect to remote servers (From my company, from my customers), I do not have the hand to personalize the PS1 and other script launch from .bashrc or .bash_profile

So User experience is not very good when I connect through ssh on distant server. (most of time i need to ssh with an other terminal)

# Solution proposal option
Currently we can globally choose the use of a PS1 (See CURRENT-SETTING screenshot)

It would be great if we could enable/disable custom PS1 when ssh distant server.

To go further, if we could list the servers on which we want to use the custom PS1 would be great
Is your feature request related to a problem? Please describe.

No response

Additional context

CURRENT-SETTING:
image

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 merge metrics
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.