Skip to content

bug(transcript): copying a wrapped command from the transcript inserts hard line breaks, so the pasted command breaks #3210

Open

Description

@QuBiit0

Before submitting

  • I searched open and closed issues and did not find a report of this problem.
  • I reviewed this report and removed credentials, tokens, private paths, hostnames, and other sensitive data.

Problem

When the assistant gives a long single-line command in a fenced code block, the transcript wraps it at the terminal width. Selecting and copying it from the screen copies the wrap points as real newlines, so pasting into a shell splits one command into several lines and it fails or behaves differently. It happened in 4 of 4 attempts in one session, with bash and PowerShell commands. In one case the command "succeeded" but wrote a broken file: a comment line was split and its second half was left without # in an env template file.

Steps to reproduce

  1. Ask the agent for a single-line command longer than the terminal width, inside a fenced code block (for example a PowerShell Add-Content -Value "...long string...").
  2. Select the command on screen with the mouse and copy it.
  3. Paste it into PowerShell 7.
  4. The shell shows >> continuation prompts at each visual wrap point, and the command splits there.

Expected and actual behavior

Expected: the copied text matches the logical line in the code block; soft wraps are not copied as newlines.
Actual: every visual wrap becomes a hard newline in the clipboard. Example: # Tango SQL adapter (ERP_ADAPTER=tango_sql). and Read-only login; ... arrived as two separate lines.

gentle-pi version

4.7.0

Pi version

1.5.1

Operating system

Windows

Relevant logs or error output (optional)

PS <project>> for f in <file-a> <file-b>; do printf '\n# Tango SQL adapter (ERP_ADAPTER=tango_sql).
>>  Read-only login; the password goes to the secret store.\nTANGO_SQL_HOST=...
ParserError: Missing opening '(' after keyword 'for'.

Terminal: Orca's integrated terminal on Windows 11, PowerShell 7. Not yet checked in Windows Terminal, so the terminal's own selection handling cannot be excluded. Related: #2578 (copy a block as plain text), which would give a workaround.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions