Skip to content
The Chat Archive
mistral-medium-2505· Mistral AI LMArena Human Preference 140K

"Simply embedding a terminal doesn't cut it. It needs to copy what jetbrains did with…

  1. User

    "Simply embedding a terminal doesn't cut it. It needs to copy what jetbrains did with their new terminal, i.e. comint mode. I want to replace foot with zed. Otherwise I stay in terminal." What do they mean by "comint mode" w/r/t jetbrains?

  2. Assistant

    The user is referring to Comint mode (short for "Command Interpreter mode"), a feature in Emacs that provides a powerful and interactive way to handle shell-like environments within a text editor. JetBrains' new terminal implementation in their IDEs (like IntelliJ IDEA, Fleet, or Zed) likely draws inspiration from this concept, offering a more integrated and editor-aware terminal experience rather than just embedding a basic terminal emulator.

    What "Comint mode" means in this context:

    1. Interactive Command Handling

      • Unlike a simple terminal emulator (like foot), Comint mode allows the editor to deeply integrate with the shell, enabling features like:
        • Command history navigation (with editor-like keybindings).
        • Inline command editing (e.g., modifying a command before executing it).
        • Better integration with the editor's UI (e.g., clickable paths, inline previews, or command suggestions).
    2. Editor-Aware Terminal

      • JetBrains' terminal likely goes beyond just running a shell; it might:
        • Parse command output to make paths, URLs, or errors clickable.
        • Allow inline editing of commands (e.g., pressing Ctrl+P to cycle through history like in a text editor).
        • Support rich text rendering (e.g., syntax highlighting, hyperlinks, or embedded images).
        • Tight integration with the IDE (e.g., detecting errors and linking them to code files).
    3. Why the User Prefers This Over foot

      • foot is a lightweight terminal emulator, but it doesn’t integrate with the editor’s features. The user wants Zed’s terminal to behave more like an editor-embedded shell (like JetBrains' implementation) rather than just a standalone terminal.

    What the User is Asking For:

    • A terminal in Zed that feels like part of the editor, with features like:
      • Command history with editor-like navigation (not just shell history).
      • Clickable output (e.g., file paths, errors, or URLs).
      • Better command editing (e.g., modifying a command before execution).
      • Tighter integration with Zed’s UI (e.g., inline previews, command suggestions).

    If Zed’s terminal is just a basic embedded terminal (like foot), the user would prefer to stay in their standalone terminal. But if Zed can replicate JetBrains' approach (inspired by Comint mode), they’d switch.

    Would you like details on how JetBrains' terminal specifically works?

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.