71–80 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.
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…
OMG UTF8! Next I suppose someone will show me how to disable those !@#%ing colour control codes that always make my text blink? I don't want colour. I don't want syntax highlighting. I just want my old-school terminal. Mind you I'll probably have to sacrifice my cherished 8x15bold font (still installable after all these years) if I really want to go UTF8.
xterm -cm> ...it turns out xterm has incredibly low input latency compared to modern terminals. This boggles my mind. What on earth does a windowed terminal need to do that should result in any latency on a modern machine? We had full ANSI-addressible displays that ran faster than the eye could read over serial lines in the 1980s. What on earth additional does a terminal program do and why would I want that?
Earlier quoted context omitted.
This is something that I never learnt how to do with Xterm, I put the keybinding in Bash: bind -x '"\C-T": _terminal_here' I would love to know how to execute a command from Xterm directly, I am sure that it is possible.
Try this: XTerm.vt100.translations: #override \n\ Ctrl T: spawn-new-terminal()
Earlier quoted context omitted.
Sure: xterm a client of your display and keyboard and mouse, remote input and output services that the X11 server provides over the network. And at the same time, a web browser is the client of computing and data servers in the cloud, provided over the network. In reality, there can be many different client/server relationships existing in different directions over the same full duplex network connection. It's really…
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.
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. :)
> ...it turns out xterm has incredibly low input latency compared to modern terminals. This boggles my mind. What on earth does a windowed terminal need to do that should result in any latency on a modern machine? We had full ANSI-addressible displays that ran faster than the eye could read over serial lines in the 1980s. What on earth additional does a terminal program do and why would I want that?
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…
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 than the Alto I used in the 70s.
> ...it turns out xterm has incredibly low input latency compared to modern terminals. This boggles my mind. What on earth does a windowed terminal need to do that should result in any latency on a modern machine? We had full ANSI-addressible displays that ran faster than the eye could read over serial lines in the 1980s. What on earth additional does a terminal program do and why would I want that?
Yet nearly every serial terminal from that era tends to struggle to handle text at >9600bps without some form of flow control at some point.
I use a mixed environment. My servers are FreeBSD, OpenBSD, and about 5 different linux distros. I can only get consistent screen output if I use Xterm. rxvt, Alcrtty (sp?), Konsole, Gnome Terminal and all others that I have tried mungle ncurses, and/or other screen decorations (like using ASCII +------+, or TAB/Space, "decorations"). Even if I do get rxvt dialed in from one client, if I connect from a different work…
Many years ago, I was surprised to find out that XTerm can also emulate a vector-based tektronix terminal. The only application for it that I found was a previewer for TeX's dvi files that could render on the Tektronix terminal by drawing a lot of tiny horizontal lines.