Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rio: Terminal app built over WebGPU, WebAssembly and Rust

github.com

Post reply on HN
Print view View original

111–120 of 134 posts

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#111

Post by tambourine_man »

JdeBP wrote: post #90
tambourine_man wrote: post #40

Earlier quoted context omitted.

Apple didn’t get the memo it seems. Terminal.app has been unchanged in many, many years. I still stubbornly use it as my daily driver for some probably terrible reason.

Did anyone actually send Apple a memo? At https://github.com/termstandard/colors#not-supporting-trueco... there are pointers to where people have asked, when they have. There's nothing for Terminal.App. (That's the big push that I mentioned. Going since January 2014.)

I don’t know where or who we would address it to. “Feedback” is such a black whole.

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#112

Post by alwillis »

sjm wrote: post #42
norman784 wrote: post #9

My question is what's their selling point, I used the past few years few terminals that have pretty good features: - Alacritty minimal and blazingly fast - Wezterm with batteries included - Warp even batteries included

Yeah I'd love to know what this is aiming for over WezTerm, which already supports both WebGPU and OpenGL rendering. Maybe just that it is closer to being able to run in a browser? I have to take a moment to just evangelize WezTerm a bit. I switched over from iTerm in the last few months and IMO WezTerm's absolute killer feature is its Lua-based configuration. You can do so much with it, down to running scripts on ke…

+1 for WezTerm. Switched from iTerm2 a while ago and have been very happy with it. Its configurability is next level.

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#113

Post by pdimitar »

graypegg wrote: post #88
pdimitar wrote: post #85

Kinda off-topic: what's the fastest terminal for macOS these days?

Nothing to back this up, but alacrity?

Yeah I am using it already. But recently I saw a thread here on HN that measured terminals by other means than what Alacritty advertises... and it was actually one of the slowest. Hence I got slightly curious but not enough to pursue deeply.

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#114

Post by yakubin »

JdeBP wrote: post #107
yakubin wrote: post #99

Earlier quoted context omitted.

I actually have the opposite problem. I’d like to limit terminal apps to just the 16 colours I have defined in my terminal settings (which is actually 3 colours in my case), but some apps (like the rust compiler e.g.) emit escape sequences which slightly change the shade in some places, in 256 colour space. I’d like to disable those 256 colours and limit everything to 16. I don’t think I can though.

As a rust programmer, you can explain to us where in this source code the rust compiler is emitting these escape sequences for colours outwith the AIXTerm 16 colour set. * https://github.com/rust-lang/rust/blob/master/compiler/rustc...

I don't see it here, but one example would be help messages saying "consider introducing lifetime `'bla` here", which are preceded with a source code quote saying something like:

  fn foo(...)
According to cat -v, is preceded by ^[[38;5;10m, which, according to [1], "applies extended color value to the foreground", and further that 38;5; sets "foreground color to index in 88 or 256 color table".

[1]: https://learn.microsoft.com/en-us/windows/console/console-vi...>

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#115

Post by JdeBP »

Patrick_Devine wrote: post #102
tambourine_man wrote: post #83

Earlier quoted context omitted.

Have you tried messing with the line height in preferences? The font panel will allow you to set whatever you please

Yes, but I shouldn't have to do that, particularly when it works correctly in most other terminals.

Spare a thought for we developers of terminal emulators. The block and line drawing characters have been being bodged since the time that IBM added the extra 9th column in hardware.

I have a fairly trivial bodge for them in mine. Kovid Goyal over a period of 7 years has built up an extensive system for overriding the glyphs for block and line drawing characters that are supplied in fonts and replacing them with ones that Kitty constructs itself, all started because they just didn't line up when using what the fonts supplied.

* https://github.com/kovidgoyal/kitty/issues/16

* https://github.com/kovidgoyal/kitty/blob/28b84a2d5b2720b88fd...

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#116

Post by yakubin »

tambourine_man wrote: post #110
yakubin wrote: post #99

Earlier quoted context omitted.

I actually have the opposite problem. I’d like to limit terminal apps to just the 16 colours I have defined in my terminal settings (which is actually 3 colours in my case), but some apps (like the rust compiler e.g.) emit escape sequences which slightly change the shade in some places, in 256 colour space. I’d like to disable those 256 colours and limit everything to 16. I don’t think I can though.

I think you can set how the terminal presents itself in both tmux and regular Terminal.app If the app doesn’t check for support and simply spills the control characters, there may be garbled output.

I've tried switching this setting in Terminal.app and all it seems to do is change the value of the TERM environment variable. I haven't observed any other effect.

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#117

Post by fnordpiglet »

wvenable wrote: post #39
JdeBP wrote: post #30

I have news for whoever did that screen shot: 256 colours is not "all colours" nowadays. (-: There was a real push, which must be approaching a decade ago at this point, to get all terminal emulators able to understand the ITU-T T.416 control sequences for direct 24-bit RGB colour. Even if they implement it really badly , and some do, almost everyone tries to support this colour system now. See the screenshot of the…

256 colors ought to be enough for anybody.

That’s like 254 too many.

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#118

Post by JdeBP »

yakubin wrote: post #114
JdeBP wrote: post #107

Earlier quoted context omitted.

As a rust programmer, you can explain to us where in this source code the rust compiler is emitting these escape sequences for colours outwith the AIXTerm 16 colour set. * https://github.com/rust-lang/rust/blob/master/compiler/rustc...

I don't see it here, but one example would be help messages saying "consider introducing lifetime `'bla` here", which are preceded with a source code quote saying something like: fn foo (...) According to cat -v , is preceded by ^[[38;5;10m, which, according to [1], "applies extended color value to the foreground", and further that 38;5; sets "foreground color to index in 88 or 256 color table". [1]: https://learn.mi…

Oh dear. You will I hope not be too embarrassed by learning that the 10 in SGR 38;5;10 (that control sequence) is colour index 10, which is less than 16, and a member of the very AIXTerm 16 colour set that you want. Thus the rust compiler is not in fact using a colour outwith the 16 AIXTerm colours.

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#119

Post by JdeBP »

tambourine_man wrote: post #111
JdeBP wrote: post #90

Earlier quoted context omitted.

Did anyone actually send Apple a memo? At https://github.com/termstandard/colors#not-supporting-trueco... there are pointers to where people have asked, when they have. There's nothing for Terminal.App. (That's the big push that I mentioned. Going since January 2014.)

I don’t know where or who we would address it to. “Feedback” is such a black whole.

Is Apple making Microsoft look good by comparison, again? (-:

Microsoft Terminal has a whole open GitHub issues system to itself.

* https://github.com/microsoft/terminal/issues/

Post reply on HN