3 ms·

I use the term "terminal emulator" in the same sense as in the blog post: "The terminal itself Shell startup is only half the story, because the emulator adds

I use the term "terminal emulator" in the same sense as in the blog post: "The terminal itself Shell startup is only half the story, because the emulator adds its own input latency. I use Ghostty, which is GPU-accelerated and native, and my config is just seven lines long." I do not use Ghostty or anything similar^1 1. https://en.wikipedia.org/wiki/List_of_terminal_emulators https://en.wikipedia.org/wiki/List_of_terminal_emulators Further, the terminal emulator cited by the blog author requires a graphics driver I do not use a graphics driver

JdeBP 5mo ago
> I do not use a graphics driver. Yes you do. It's the one that your in-kernel terminal emulator talks to in order to splat its bitmap fonts onto the screen. It is whatever wsdisplay has attached to, which can be one of a range of things from genfb through voodoofb and machfb to radeonfb. There was even a vesafb about 20 years ago.
deleted 5mo ago
[deleted]
1vuio0pswjnm7 5mo ago
"I do not use a graphics driver" Maybe this is not clear. I apologise for any ambiguity vga(4) can be referred to as a "graphics driver" For example, https://man.netbsd.org/vga.4 https://man.netbsd.org/vga.4 But it does not support (non-text) graphics It only supports text The blog author is using a graphics layer such as X11 or Wayland along with a terminal emulator such as Ghostty on top of it I do not use those things
- deleted 5mo ago
  [deleted]
1vuio0pswjnm7 5mo ago
To be more clear, I use a "graphics driver" but only in textmode. Perhaps a better statement would be "I do not use a graphics mode" https://man.netbsd.org/vga.4 https://man.netbsd.org/vga.4 "VGA graphics driver" "This driver handles VGA graphics..." I only use VGA textmode I do not context switch into a graphics mode via 13h. No need The blog author mentions that his terminal emulator is "GPU-accelerated" ("GPU" stands for "Graphic Processing Unit") I don't use a terminal emulator that requires a graphics mode or one that uses a GPU I'm interested in "text processing", displaying text. I like reading I'm not interested in displaying images
1vuio0pswjnm7 5mo ago
Terminal emulators such as Ghostty usually depend on a "desktop" environment such as GNOME, KDE, etc. I do not use a "desktop" environment As such, I do not need the dependencies of such terminal emulators, such as "gtk" ("GIMP ToolKit") a widget toolkit for creating GUIs ("Graphical User Interfaces") As I am only using the command line, not a "desktop", I have no need for a GUI toolkit
1vuio0pswjnm7 5mo ago
To be clear, I only use the VGA driver,^1 I do not use it to display non-text graphics, e.g., images, and I do not use a framebuffer on NetBSD^2 The blog author is using more than the VGA driver to display text, as indicated by the reference to "GPU-accelerated" 1. Some call this a "graphics driver" while others state it "does not do graphics" 2. For example, drivers with names ending in "fb", such as "vesafb"

JdeBP 5mo ago

> I do not use a graphics driver. Yes you do. It's the one that your in-kernel terminal emulator talks to in order to splat its bitmap fonts onto the screen. It is whatever wsdisplay has attached to, which can be one of a range of things from genfb through voodoofb and machfb to radeonfb. There was even a vesafb about 20 years ago.

deleted 5mo ago

[deleted]

1vuio0pswjnm7 5mo ago

"I do not use a graphics driver" Maybe this is not clear. I apologise for any ambiguity vga(4) can be referred to as a "graphics driver" For example, https://man.netbsd.org/vga.4 https://man.netbsd.org/vga.4 But it does not support (non-text) graphics It only supports text The blog author is using a graphics layer such as X11 or Wayland along with a terminal emulator such as Ghostty on top of it I do not use those things

deleted 5mo ago
[deleted]

1vuio0pswjnm7 5mo ago

To be more clear, I use a "graphics driver" but only in textmode. Perhaps a better statement would be "I do not use a graphics mode" https://man.netbsd.org/vga.4 https://man.netbsd.org/vga.4 "VGA graphics driver" "This driver handles VGA graphics..." I only use VGA textmode I do not context switch into a graphics mode via 13h. No need The blog author mentions that his terminal emulator is "GPU-accelerated" ("GPU" stands for "Graphic Processing Unit") I don't use a terminal emulator that requires a graphics mode or one that uses a GPU I'm interested in "text processing", displaying text. I like reading I'm not interested in displaying images

1vuio0pswjnm7 5mo ago

Terminal emulators such as Ghostty usually depend on a "desktop" environment such as GNOME, KDE, etc. I do not use a "desktop" environment As such, I do not need the dependencies of such terminal emulators, such as "gtk" ("GIMP ToolKit") a widget toolkit for creating GUIs ("Graphical User Interfaces") As I am only using the command line, not a "desktop", I have no need for a GUI toolkit

1vuio0pswjnm7 5mo ago

To be clear, I only use the VGA driver,^1 I do not use it to display non-text graphics, e.g., images, and I do not use a framebuffer on NetBSD^2 The blog author is using more than the VGA driver to display text, as indicated by the reference to "GPU-accelerated" 1. Some call this a "graphics driver" while others state it "does not do graphics" 2. For example, drivers with names ending in "fb", such as "vesafb"