3 ms·

Something that I noticed recently is that the latency/input lag feels lower in xterm compared to unicode-rxvt. I used urxvt from ~2011 until a couple of months

by jd3 6y ago

Something that I noticed recently is that the latency/input lag feels lower in xterm compared to unicode-rxvt. I used urxvt from ~2011 until a couple of months ago and I have been really liking the speed and simplicity of xterm since then.

3np 6y ago
Maybe we have some difference in configuration, but I don't have any perceivable difference between the two - still on urxvt since way back. Background transparency is the one feature keeping me from considering xterm. I like the URL handling hack in OP, but I'm also a bit married to some urxvt plugins (URL handler, trimming whitespace when copying)
- jd3 6y ago
  > Maybe we have some difference in configuration, but I don't have any perceivable difference between the two - still on urxvt since way back. I think the entirety of my ~/.xresources xterm config is #include ".Xresources.colors" !! xterm ! https://invisible-island.net/xterm/ ! https://linux.die.net/man/1/xterm !XTerm.vt100.faceName: Monaco:pixelsize=11 XTerm.scrollTtyKeypress: true XTerm.scrollTtyOutput: false XTerm.utf8: true XTerm.vt100.boldMode: false XTerm.vt100.locale: false XTerm.vt100.scrollbar.width: 8 XTerm.vt100.scrollBar: true XTerm.vt100.utf8: true I'll try to take a video of the difference at some point — I use xorg 1.20.8 on macOS 11.1 and it definitely feels noticeable when I type quickly with vsync disabled (through Quartz Debug.app). > Background transparency is the one feature keeping me from considering xterm. That's fair. The macOS xorg server has never supported the COMPOSITE extension/xcompmgr/compiz, so transparency/compositing have always been out of the question for me. > I like the URL handling hack in OP, but I'm also a bit married to some urxvt plugins (URL handler, trimming whitespace when copying) I sympathize with this — I used urxvt for years and grew to like how it could easily extend itself using perl. Thankfully, I have been able to mirror all of my urxvt functionality in xterm since I switched back. It also helped me simplify my ~/.xresources, which shrank from ~300 lines 10 years ago to 50 (for both my xterm and urxvt configs excluding color definitions, which live in ~/.Xresources.colors).

by jd3 6y ago

3np 6y ago

Maybe we have some difference in configuration, but I don't have any perceivable difference between the two - still on urxvt since way back. Background transparency is the one feature keeping me from considering xterm. I like the URL handling hack in OP, but I'm also a bit married to some urxvt plugins (URL handler, trimming whitespace when copying)

jd3 6y ago
> Maybe we have some difference in configuration, but I don't have any perceivable difference between the two - still on urxvt since way back. I think the entirety of my ~/.xresources xterm config is #include ".Xresources.colors" !! xterm ! https://invisible-island.net/xterm/ ! https://linux.die.net/man/1/xterm !XTerm.vt100.faceName: Monaco:pixelsize=11 XTerm.scrollTtyKeypress: true XTerm.scrollTtyOutput: false XTerm.utf8: true XTerm.vt100.boldMode: false XTerm.vt100.locale: false XTerm.vt100.scrollbar.width: 8 XTerm.vt100.scrollBar: true XTerm.vt100.utf8: true I'll try to take a video of the difference at some point — I use xorg 1.20.8 on macOS 11.1 and it definitely feels noticeable when I type quickly with vsync disabled (through Quartz Debug.app). > Background transparency is the one feature keeping me from considering xterm. That's fair. The macOS xorg server has never supported the COMPOSITE extension/xcompmgr/compiz, so transparency/compositing have always been out of the question for me. > I like the URL handling hack in OP, but I'm also a bit married to some urxvt plugins (URL handler, trimming whitespace when copying) I sympathize with this — I used urxvt for years and grew to like how it could easily extend itself using perl. Thankfully, I have been able to mirror all of my urxvt functionality in xterm since I switched back. It also helped me simplify my ~/.xresources, which shrank from ~300 lines 10 years ago to 50 (for both my xterm and urxvt configs excluding color definitions, which live in ~/.Xresources.colors).