81–90 of 159 posts
I've found the latency of Konsole to be phenomenally low. I can definitely tell the difference between Konsole and GTK-based terminals, but I can't really tell the difference between the latency of Konsole and XTerm.
never understood whar extra features people need out of a terminal that they are building new ones. heck there are electron based terminals
Earlier quoted context omitted.
Well, it first needs to take the your input and pass it through the HID subsystem into userspace to the appliction, which then responds to it and sends it to the terminal, wjocj collects the output and then emulates whatever control codes there are, then updates its internal model of whatever PTY thing it is emulating, then sends that to the screen and wait for the window server to pick up on those changes and then d…
But my point is that an Ann Arbor Ambassador terminal (with logic, not even an 8-bit processor) talking to a VAX 750 (about 1/2 MIPS, also passing data from kernel into user space) was lightning fast. The internal processor that does nothing but scan my laptop's keyboard to send events to the "computer" is more powerful than the setup we used to have. Yet the entire thing is slower. My Mac doesn't draw any faster tha…
Yes it absolutely does, you just don't notice because of the increase in fidelity. What was then 640x480 pixels is now a 4K display. The total number of pixels is several orders of magnitude more, the number of colors is now 16.7 million rather than 256, and the complexity of the scene has increased where we now have anti-aliased text and alpha blending.
Earlier quoted context omitted.
Try this: XTerm.vt100.translations: #override \n\ Ctrl T: spawn-new-terminal()
That opens the new terminal in the home directory, right? My keybind opens it in whatever directory I’m already in which I find handy in deeply nested projects.
All these Xorg/X11 problems people complain about... I honestly don't see them. I've been using Xorg in one form or another since 2005-2006 and frankly since we all got automatic configuration and said godbye to Xorg.conf it's been a very very pleasant experience. I've been using both nVidia and intel cards, 1/2/3 monitors (in various arrangement) and network stuff (ssh -X and similar), and a videogame from time to t…
That's because DonHopkins is shitposting quotes from the Unix Haters Handbook, which came out in 1994 and contains gripes about Unix dating back to the 80s.
The Unix ecosystem, including X11, evolved a teensy tiny bit since then.
I use xterm because I'm too lazy to switch, I guess. It was never bad enough for me to switch and it's present virtually everywhere, so I don't need to bother installing my favorite niche term (kind of like sticking with bash when zsh was indisputably more awesome). To the best of my knowledge, one downside is the text rendering is synchronous. Read a character off the tty, try to display it on the screen. It's fine…
I use xterm because it's one of the only terminal emulators that allows me to disable the alt-screen (titeInhibit). Apparently I'm one of the few, but when I vi/view a file and exit, or read a man page and go back to the command line, I still want to be able to reference what I was just looking at.
`xterm` lacks Wayland support-- a more secure alternative to X11. For a fast terminal with Wayland support, check out `alacritty` or foot: https://codeberg.org/dnkl/foot `foot` (foo terminal) benchmarks faster than alacritty and offers a client/server mode for even faster startup for new terminal windows.
What I'd expect to find is some description of the security guarantees they provide, and some active work (such as fuzzing with hostile clients), and tracking of found & fixed vulnerabilities.
Yeah, I'd say xterm is pretty freakin' awesome. While Hackernews was busy grooming their Alacritty setup and holding drag races between it, iTerm, and whatever bloated terminal Microsoft came up with to see which could cat a huge file the fastest, I've been just using xterm. xterm -- it's the standard terminal emulator. xterm: * actually emulates a terminal and passes a set of compliance tests to determine how VT-com…
I'm not familiar with the history, but I guess this is essentially referring to a standard defined by hardware products from the 1970s? Why is that still relevant?
Earlier quoted context omitted.
Only the server, actually serves the graphics to the user. Within the context of the X Window System, the server is the body of code responsible for delivering the display to the user viewing it.
> Only the server, actually serves the graphics to the user. The server actually serves the user to the remote client. It's like "you are not the customer, you are the product". The remote program needs to communicate graphically with you, and connects to the X server to do this; therefore, you are not the requester of a resource, you are the resource being served. :)
I've found the latency of Konsole to be phenomenally low. I can definitely tell the difference between Konsole and GTK-based terminals, but I can't really tell the difference between the latency of Konsole and XTerm.
never understood whar extra features people need out of a terminal that they are building new ones. heck there are electron based terminals
I have a 4K display and terminal has it's own virtual desktop, separating a Konsole window into nested tabs is a must to simplify the navigation between tabs since you can switch to other groups by a single hotkey.
I use profiles to visually differentiate tabs for different purposes (e.g. ssh to hosts with master and replicas of DBMS, which I did years prior to [0] happened), some made for fixing production hosts so they have an infinite logging enabled, and one can alter hotkey schemes with those.
Alarms are just an easy way of triggering a notification when a task is done or failed, saves time and brain resources.