VTE-Based Linux Terminals Now Support A Nice Feature Led By Windows Terminal

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ssokolow
    replied
    Originally posted by Quackdoc View Post

    wait, that's what this is about? man I could not care less lmao
    It's possible the VTE-based terminals also use the information elsewhere... but the part about exposing it so the terminal has the ability to tell the information apart from just random updates to the character cell canvas is the only part of the article that's crystal clear.

    With Windows Terminal the sequences can be used for displaying a spinner on the terminal tab, for example, during long running processes.
    (Plus showing an in-tab progress pie chart in that screenshot of Ptyxis.)

    Leave a comment:


  • Quackdoc
    replied
    Originally posted by ssokolow View Post

    This is about putting a little "progress pie chart" indicator in the tab.

    It's akin to that xterm escape sequence that lets you change the window title or that Unity/Plasma API which only works for installed applications (no Appimage. The D-Bus API is incomplete-by-design and requires installed .desktop files to map IDs to processes.) which lets something like copying a file in your file manager display a progress bar in its taskbar entry.

    (Hah! There's one use for this. We can fix the Unity/Plasma progress API once Konsole supports this by writing TUI apps that don't need to be installed and letting Konsole play XDG Portal and bridge it into the Unity/Plasma taskbar progress API.)
    wait, that's what this is about? man I could not care less lmao

    Leave a comment:


  • pong
    replied
    Originally posted by Old Grouch View Post

    It might be better visually, but it is better for people using screen-readers - the blind and partially-sighted? Eye-candy is all well and good, but if it makes things worse for the visually impaired, it should not be released.

    I don't know if this does, or doesn't.

    A standard for terminals that makes progress bars accessible in a clear way for screen readers would be excellent.
    That and also just the general "readability" of things when you're making a transcript / log of the session and it looks fine on screen but the log is filled with useless spew of non-rendered escape sequences instead of any kind of semantically relevant "here's what happened over time" list or something.

    The "how this is rendered visually on the screen" "view" of something is a distinct thing from "what is the semantic information being represented by this screen at this time" "snapshot" and the latter is critical for accessibility and also just sanity in reviewing histories or composing some kinds of interpretive pipelines / agents based on the output of programs or for purposes like language translation, mirroring (semantic) content via screen sharing, making copy-paste work sanely, etc.

    Leave a comment:


  • pong
    replied
    Originally posted by ahrs View Post

    Konsole has this too. You can easily wrap any command in notify-send though to send a notification after running any long-running command, of course sometimes you might forget to do that and wish you'd done so after the fact.
    I haven't used / known about that. But just a naive impression suggests that it might
    not be hard conceptually to do it for processes already running. After all one typically has job control, 'ps' process status, signal based notifications, etc. etc. so lots of ways to monitor / interact with running processes. So why not be able to set a notification wrt. an already running process's events?

    Leave a comment:


  • varikonniemi
    replied
    Originally posted by kpedersen View Post

    Indeed. These overly featureful terminals just feel slushy and messy. I prefer my terminal not to have ADHD.
    the opposite of this is pacman progress bar in pacman. It makes it more readable. (not for generic terminal text to speech translators, this is why it is optional)

    Leave a comment:


  • varikonniemi
    replied
    Originally posted by elduderino View Post

    It was trivial to implement. And it's more readable because you can see it without changing tabs.

    If you mean the progress bar from the screenshot, then yeah that is absolutely absurd which is why it is a test program.
    well i thought that was the only change

    Leave a comment:


  • uid313
    replied
    Originally posted by archkde View Post

    Fbcon is basically unmaintained and if anything only getting worse (e.g. losing features) by now. Use kmscon or any terminal you like running inside a lightweight Wayland compositor instead.
    It would be nice if I could come to a terminal running inside a Wayland compositor by pressing Ctrl+Alt+F1.

    Leave a comment:


  • elduderino
    replied
    Originally posted by Old Grouch View Post
    It might be better visually, but it is better for people using screen-readers - the blind and partially-sighted? .
    That is a great question.

    And as one of the few people who've actually implemented a11y for a terminal I can tell you we could definitely do a better job with the escape sequence than what is done with contents of the terminal screen (which in most implementations are diff'd from both ends to try to find the change sequence).

    With the percentage as a value to the terminal emulator, you can actually export this as an a11y property to the screen reader.

    Leave a comment:


  • Old Grouch
    replied
    Originally posted by elduderino View Post

    It was trivial to implement. And it's more readable because you can see it without changing tabs.

    If you mean the progress bar from the screenshot, then yeah that is absolutely absurd which is why it is a test program.
    It might be better visually, but it is better for people using screen-readers - the blind and partially-sighted? Eye-candy is all well and good, but if it makes things worse for the visually impaired, it should not be released.

    I don't know if this does, or doesn't.

    A standard for terminals that makes progress bars accessible in a clear way for screen readers would be excellent.

    Leave a comment:


  • fitzie
    replied
    who is still using xterm in 2024?

    Leave a comment:

Working...
X