{"version":"2.1.251","anchor":"statusline-setup-handles-shell-prompts-more-carefully","canonical_anchor":"statusline-setup-handles-shell-prompts-more-carefully","heading":"\/statusLine setup handles shell prompts more carefully","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/statusline-setup-handles-shell-prompts-more-carefully","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### \/statusLine setup handles shell prompts more carefully\n\n\/statusLine setup cleans trailing prompt characters and asks you when it finds no shell prompt.\n\n**What**\n\nThe instructions used when setting up a custom status line now say to strip trailing `$` or `>` characters when importing your shell prompt, and to ask you what you want if no shell prompt is found and you gave no instructions.\n\n**Evidence**\n\n`If the imported PS1 would have trailing \"$\" or \">\" characters in the output, you MUST remove them.`\n\n- Area: Terminal UI\n- Names: `\/statusLine`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}