Skip to content

Console features #20

@timonmdy

Description

@timonmdy

Text handling

  • Carriage return (\r) support — batch scripts use \r\n and some tools rewrite the current line using \r alone (progress bars, download indicators). Slitter at \r?\n strips \r but mid-line \r rewrites are not handled, so you would see garbled output instead of an overwritten line.
  • Wide/fullwidth character handling — CJK characters take two columns but are treated as one, breaking alignment in table output.

ANSI / terminal sequences beyond SGR

  • Cursor movement (\x1b[A up, \x1b[B down, \x1b[G column, \x1b[2K erase line) — tools like progress bars, spinners, and interactive CLIs use these to rewrite previous lines. Currently stripping them as garbage.
  • OSC sequences (e.g. window title setting \x1b]0;title\x07) — currently leak raw bytes into output.
  • Hyperlinks (\x1b]8;;url\x07text\x1b]8;;\x07) — some modern CLI tools emit clickable links.

Input

  • No Tab completion
  • No stdin raw mode / password input — some tools prompt for passwords and expect no echo. Input always echoes.

Output

  • No timestamps per line — a dedicated runner can do better. Implement a setting for this.
  • No line-level copy button / right-click copy
  • Enable history/long-term logging per profile. Add a new main tab for the logs to be viewed per session and a toggle in General sub-tab which is off by default. Save logs as normal .log files and start them from the start signal and save them at stop signal. Append stop-timestamp to file name. Save the logs in the config directory per profileId

Process interaction

  • No environment variable injection per-profile — batch files can set env vars before the call; JRC has JVM args and system properties but not raw env overrides.
  • No working-directory-relative file open — batch users can type start notepad output.log in the same shell. Not applicable 1:1 but opening the working directory in Explorer is a common need.
  • "Gently" stopping a process: Processes are currently always killed instead of askin them to shut down. Implement logic like in IntelliJ IDEA

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions