18 ms·
XTerm: It's Better Than You Thought
- MarkusWandel 6y agoOMG 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.
- BikiniPrince 6y agoI do! I use the terminal everything and even my IDE. Give me all the fancy features and dream up more. Just actually support vt100 when it is needed and in sometimes worse situations. Our “serial” console solution is even worse then the old school days. God help us if we need to use it for more then the occasional evaluation.
- epilys 6y agoYou might be interested in https://no-color.org/ https://no-color.org/ I implemented it for my mail client (listed on the website)
- dn3500 6y agoI set TERM=vt102 to get rid of the garish colors. You still get the basic colors, which can be useful sometimes.
- fanf2 6y agoYou might like the showBlinkAsBold Xresources setting https://www.freebsd.org/cgi/man.cgi?query=xterm&apropos=0&sektion=0&manpath=FreeBSD+12.2-RELEASE+and+Ports&arch=default&format=html https://www.freebsd.org/cgi/man.cgi?query=xterm&apropos=0&se...
- shakna 6y agoIf you want no colors with xterm? xterm -cm
- teddyh 6y agoMy absolutely essential XTerm settings: ! Convert Meta-x into "ESC x", not "ø" XTerm.VT100.metaSendsEscape: true ! Allow HT (TAB) in paste; i.e. do not convert to space character XTerm*VT100.DisallowedPasteControls: BS,DEL,ESC ! Assume window titles are UTF-8 encoded XTerm.VT100.utf8Title: true (Add to your ~/.Xresources and/or ~/.Xdefaults file.)
- asguy 6y agoFor people interested in playing around with different terminal emulators, you’d do yourself a service trying kitty [https://github.com/kovidgoyal/kitty https://github.com/kovidgoyal/kitty]. It made my experience on high DPI screens far better. You can find it packaged up in the usual places (e.g. Debian).
- jasonjayr 6y agoI've recently taken up alacritty (+ tmux), which is fast; nice, and scales on displays sensibly. I'd been using urxvt w/ a plugin for tabs for eons previously. I'be been mutating my tmux config to match the urxvt + screen binding I've been used to.
- dharmab 6y agoI switched to kitty because it supports a killer feature I became accustomed to in iTerm- a keybind for "Open a new terminal in the same directory as the current terminal."
- DonHopkins 6y agohttps://medium.com/@donhopkins/the-x-windows-disaster-128d398ebd47 https://medium.com/@donhopkins/the-x-windows-disaster-128d39... The Nongraphical GUI XCalc After Several Resizings https://miro.medium.com/max/434/0*LIDAYbj5NRANRGl7.gif https://miro.medium.com/max/434/0*LIDAYbj5NRANRGl7.gif X was designed to run three programs: xterm, xload, and xclock. (The idea of a window manager was added as an afterthought, and it shows.) For the first few years of its development at MIT, these were, in fact, the only programs that ran under the window system. Notice that none of these program have any semblance of a graphical user interface (except xclock), only one of these programs implements anything in the way of cut-and-paste (and then, only a single data type is supported), and none of them requires a particularly sophisticated approach to color management. Is it any wonder, then, that these are all areas in which modern X falls down? Ten years later, most computers running X run just four programs: xterm, xload, xclock, and a window manager. And most xterm windows run Emacs! X has to be the most expensive way ever of popping up an Emacs window. It sure would have been much cheaper and easier to put terminal handling in the kernel where it belongs, rather than forcing people to purchase expensive bitmapped terminals to run character-based applications. On the other hand, then users wouldn’t get all of those ugly fonts. It’s a trade-off.
- SllX 6y agoHere’s a non-Medium version[1], since Medium is similarly but completely unrelatedly, a disaster. [1]http://www.art.net/~hopkins/Don/unix-haters/x-windows/disaster.html http://www.art.net/~hopkins/Don/unix-haters/x-windows/disast...
- Steltek 6y agoI 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 until you go and cat /dev/mem or something like that. Many GNOME-ish terminals use vte which drops frames if it can't keep up rendering. I also run into problems with bad display managers or DEs that don't load ~/.Xresources or ~/.Xdefaults (looking at you Debian gdm).
- bitwize 6y ago> To the best of my knowledge, one downside is the text rendering is synchronous. I find this to be a feature, it's part of what makes xterm a terminal emulator. There's a speedhack in recent xterm that makes it behave more like libvte, but I forgot the incantation to enable it.
- padthai 6y ago> Many GNOME-ish terminals use vte which drops frames if it can't keep up rendering. Cannot you that with Xterm too? XTerm*fastScroll: true
- linsomniac 6y agoI 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.
- DonHopkins 6y agohttps://medium.com/@donhopkins/the-x-windows-disaster-128d398ebd47 https://medium.com/@donhopkins/the-x-windows-disaster-128d39... Date: Wed 10 Apr 91 08:14:16 EDT From: Steve Strassmann <straz@media-lab.mit.edu> To: UNIX-HATERS Subject: the display from hell I have a “window system” on my unix box. You see, in the unix world, “system” means “a bunch of unrelated programs.” But that’s not what I want to talk about here today. I want to talk about overlay planes. My HP 9000/835 console has two 19" color monitors, and some extremely expensive Turbo SRX graphics hardware to drive them. You’d think that I could simply tell X windows that it has two displays, the left one and the right one, but that would be unthinkably simple. After all, if toys like Macintoshes can do this, unix has to make it much more difficult to prove how advanced it is. So, what I really have is two display devices, /dev/crt0 and /dev/crt1. No, sorry, I lied about that. You see, the Turbo SRX display has a graphics plane (with 24 bits per pixel) and an overlay plane (with 4 bits per pixel). The overlay plane is for things like, well, window systems, which need things like cursors, and the graphics plane is to draw 3D graphics. So I really need four devices: /dev/crt0 — — the graphics plane of the right monitor /dev/crt1 — — the graphics plane of the left monitor /dev/ocrt0 — — the overlay plane of the right monitor /dev/ocrt1 — — the overlay plane of the left monitor No, sorry, I lied about that. /dev/ocrt0 only gives you 3 out of the 4 overlay bits. The fourth bit is reserved exclusively for the private use of federal emergency relief teams in case of a national outbreak of Pixel Rot. If you want to live dangerously and under threat of FBI investigation, you can use /dev/o4crt0 and /dev/o4crt1 in order to really draw on the overlay planes. So, all you have to do is tell X windows to use these o4 overlays, and you can draw graphics on the graphics plane. No, sorry, I lied about that. X will not run in these 4 bit overlay planes. This is because I’m using Motif, which is so sophisticated it forces you to put a 1" thick border around each window in case your mouse is so worthless you can’t hit anything you aim at, so you need widgets designed from the same style manual as the runway at Moscow International Airport. My program has a browser that actually uses different colors to distinguish different kinds of nodes. Unlike a PC Jr, however, this workstation with $150,000 worth of 28 bits-per-pixel supercharged display hardware cannot display more than 16 colors at a time. If you’re using the Motif self-abuse kit, asking for the 17th color causes your program to crash horribly. So, thinks I to myself cleverly, I shall run X windows on the graphics plane. This means X will not use the overlay planes, which have special hardware for cursors. This also means I cannot use the super cool 3D graphics hardware either, because in order to draw a cube, I would have to “steal” the frame buffer from X, which is surly and uncooperative about that sort of thing. What it does give me, however, is a unique pleasure. The overlay plane is used for /dev/console, which means all console messages get printed in 10 Point Troglodyte Bold, superimposed in white over whatever else is on my screen, like for example, a demo that I may be happen to be giving at the time. Every time anyone in the lab prints to the printer attached to my machine, or NFS wets its pants with a timeout, or some file server threatens to go down in only 3 hours for scheduled maintenance, another message goes onto my screen like a court reporter with Turett’s syndrome. The usual X commands for refreshing the screen are helpless to remove this incontinence, because X has no access to the overlay planes. I had to write a program in C to be invoked from some xterm window that does nothing but wipes up after the mess on the overlay planes. My super 3D graphics, then, runs only on /dev/crt1, and X windows runs only on /dev/crt0. Of course, this means I cannot move my mouse over to the 3d graphics display, but as the HP technical support person said “Why would you ever need to point to something that you’ve drawn in 3D?” Of course, HP claims X has a mode which allows you to run X in the overlay planes and “see through” to the graphics planes underneath. But of course, after 3 months of calls to HP technical support, we agreed that that doesn’t actually work with my particular hardware configuration. You see, I have the top-of-the-line Turbo SRX model (not one, but two on a single workstation!), and they’ve only tested it on the simpler, less advanced configurations. When you’ve got a hip, forward-thinking software innovator like Hewlett-Packard, they think running X windows release 2 is pretty advanced.
- nickjj 6y agoHere's a few other useful binds related to zooming out, in and resetting zoom: Ctrl <Key> minus: smaller-vt-font() \n\ Ctrl <Key> plus: larger-vt-font() \n\ Ctrl <Key> 0: set-vt-font(d) \n\ And 2 other config options to help reduce trailing spaces when selecting text: xterm*highlightSelection: true xterm*trimSelection: true
- UI_at_80x24 6y agoI 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 workstation with a different client it's all a mess again. I know xterm is the slowest of the bunch, but it always works with minimal putzing.
- AstroNoise58 6y agoMost "modern" terminals are surprisingly buggy (for lack of a better word), that is, they do not conform to the VT100-series specs (and less documented, but well known quirks). Here's a look at some of them: https://tomscii.sig7.se/2020/12/A-totally-biased-comparison-of-Zutty https://tomscii.sig7.se/2020/12/A-totally-biased-comparison-...
- padthai 6y ago> I know xterm is the slowest of the bunch, but it always works with minimal putzing. I though that Xterm was the fastest in terms of latency and configured adequately, pretty going dealing with big amounts of text: https://anarc.at/blog/2018-05-04-terminal-emulators-2/ https://anarc.at/blog/2018-05-04-terminal-emulators-2/ Xterm*fastScroll: true I am really grateful for Xterm, it is a great default for all my machines.
- Aloha 6y agoThe only way I've found to get consistency is use GNU screen as a translator.
- deleted 6y ago[deleted]
- ogogmad 6y agoDoes XTerm support unicode?
- snvzz 6y agoYes. And it should be the default if you open an xterm today.
- sprash 6y agoObviously yes. But depending on your distribution or locale settings you might have to launch the uxterm[1] wrapper instead of xterm if it doesn't work out of the box. 1.: https://invisible-island.net/xterm/manpage/uxterm.html https://invisible-island.net/xterm/manpage/uxterm.html
- markstos 6y ago`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 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.
- andrelaszlo 6y agoWhat about xclock?
- DonHopkins 6y agoWhy use xclock when you can use Sun's "clocktool"? https://medium.com/@donhopkins/the-x-windows-disaster-128d398ebd47 https://medium.com/@donhopkins/the-x-windows-disaster-128d39... X has had its share of $5,000 toilet seats — like Sun’s Open Look clock tool, which gobbles up 1.4 megabytes of real memory! If you sacrificed all the RAM from 22 Commodore 64s to clock tool, it still wouldn’t have enough to tell you the time. Even the vanilla X11R4 “xclock” utility consumed 656K to run. And X’s memory usage is increasing.
- asveikau 6y agoThis is really dated criticism. Nobody in 2021 is talking about Sun Open Look. And even that, whatever its faults at the time, was probably less resource intensive than what most HN readers would use to build a UI today. Try running electron on an Open Look era machine.
- fulafel 6y agoA tangent but where could I find a good evaluation of Wayland stack (including Weston etc) security? I know the design is often brought up but most vulnerabilities are implementation errors and bugs, and there doesn't seem to be any mention of security (advisories, etc) on the Wayland web site nor does a web search bring up anything that woudl indicate there's any active security focus. 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.
- qnxub 6y agoI'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.
- himujjal 6y agonever understood whar extra features people need out of a terminal that they are building new ones. heck there are electron based terminals
- deleted 6y ago[deleted]
- chupasaurus 6y agoI use window separation and profiles in Konsole every single day and alarms are handy when needed. 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.
- cturner 6y agoYou can get a fair bit of that with terminal multiplexers like tmux. It does not have the ability to style different tabs. But it has advantages too. For example, you can have multiple terms connected to a single tmux session, you can run tmux when ssh’d to a remote server, the tool is not tied to a particular vt. Not to say your setup is deficient, but I think I understand where the parent is coming from.
- bitwize 6y agoYeah, 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-compatible a terminal is (other TEs emulate xterm, poorly) * is still compatible with bitmap fonts * has a reputation for being slower than other TEs, but that's only because by default it doesn't cheat and commits every screen update. Other TEs, in order to increase their chances of winning the drag race, will skip updates they think you won't see. This can be enabled via a command-line option or X resource in xterm, but makes xterm less compatible. * comes with every Linux or BSD distro and works fast on nearly any graphics adapter
- alanbernstein 6y agoWhat is the practical value in better VT compatibility? 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?
- rvense 6y agoSame as adhering to any standard? The software you want to run produces VT-compatible output, the terminal consumes that and provides a display.
- alanbernstein 6y agoWhat i mean is, many other computer standards become obsolete and get replaced. What is so special about this standard from the 1970s that has given it so much staying power? It is a software standard, influenced by hardware, which has outlasted nearly every other hardware and software standard of its time. Doesn't that strike anyone else as bizarre?
- bitwize 6y ago
- mixmastamyk 6y agoIt's decent and supports direct-color and all the obscure features of xterm of course, that others don't like querying and setting the color palette. It doesn't support most(any?) of the bleeding-edge sequences for hyperlinks and underline styling. It may have better input latency than xfce, but what are you running it on, a 486? Maybe for RPi, but—it has poor paint performance as well. It will flash if you try to do animation or scroll a complex screen. Bit of a toss up on the that front. Anyway I find it useful for testing terminal sequences, but it's a tough sell as a daily driver. Things like tabs and a proper scrollbar are a minimum for me.
- tutfbhuf 6y ago> Things like tabs and a proper scrollbar are a minimum for me. I use xterm in tmux, no need for native scrollbar or tabs.
- mixmastamyk 6y agoDo you mean the reverse? I'm using a number of applications, the terminal is but one. So, I find a consistent interface is desirable.
- tutfbhuf 6y agoI like composability, to stack software together, like chaining coreutils in bash. Vim inside of Tmux inside of Xterm inside of Xorg on Linux. Every software adds its functionality to the stack, but no more.
- padthai 6y agoWhat do you mean by scrollbar? Xterm has a scrollbar, and you can customize it with plenty of options. Tabs I agree that it may be a showstopper for some, however in X you can use suckless tabbed to add support: https://tools.suckless.org/tabbed/ https://tools.suckless.org/tabbed/ For some of us, we just want the fastest terminal out there (in latency and startup), because everything else will be taken care by the window manager or Tmux.
- sprash 6y agoFurther tips that might interest people: Xterm should support sixels out of the box but needs further configuration to make it work properly: XTerm*decTerminalID: 340 XTerm*numColorRegisters: 256 If you want to scroll the content in alternate screens like less instead of the scrollback buffer with your scroll-wheel you have to enable: XTerm*alternateScroll: true If you want a subtle and less jarring visual terminal bell you can enable this option which flashes only the current line and not the whole screen: XTerm*visualBell: true XTerm*visualBellLine: true XTerm*visualBellDelay: 20
- deleted 6y ago[deleted]
- megous 6y agoxterm is sadly very slow (you see line by line re-draw in midnight commander and things like that) on glamor/GPU accelerated Xorg server on all my ARM devices. I switched to st (https://st.suckless.org/ https://st.suckless.org/) on my ARM devices, and while it has less features, it doesn't have this performance issue. I never figured why that is, other than it not being a CPU issue.
- mixmastamyk 6y agoI believe it is not buffering draws, although have never checked the source. Edit: I found this at the arch wiki: Troubleshooting - Flickering on scroll Warning: Double buffering may cause non-bitmap fonts to render incorrectly. Rebuild xterm using ABS and include the --enable-double-buffer flag: ./configure --prefix=/usr \ ... --with-utempter \ --enable-double-buffer Could be more friendly.
- megous 6y agoHmm, I confused xterm with urxvt.
- jhallenworld 6y agoYou can get a tabbed xterm this way (From stack exchange): Do sudo "apt-get install suckless-tools", then run this command to have a tabbed xterm: tabbed -c xterm -into & Press Ctrl+Shift+Enter to open a new tab and Ctrl+Q to close a tab. You'll find more info in the man page for tabbed.
- aftbit 6y agoHow can I set an arbitrary background color? I want something like 0x1A1B1C as I have for alacritty.
- deleted 6y ago[deleted]
- jhallenworld 6y agoxterm -bg '#bebebe'
- cylinder714 6y agoxterm -bg \#1A1B1C -fg white
- gumby 6y ago> ...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?
- saagarjha 6y agoWell, 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 double buffer it onto the screen…it's complicated, to say the least.
- gumby 6y agoBut 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 than the Alto I used in the 70s.
- Jasper_ 6y ago> My Mac doesn't draw any faster than the Alto I used in the 70s. 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.
- 6y ago
- dunham 6y agoMany 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.
- enriquto 6y agognuplot's tektronix graphs are quite neat, with a noble "oscilloscope" feeling
- dirkt 6y agoIf you liked the tektronix emulation, also have a look at sixel graphics [1], which also work in an xterm. Helpful if you are logged in via ssh without X forwarding, and need some graphics... [1] https://github.com/saitoha/libsixel https://github.com/saitoha/libsixel
- jd3 6y agoSomething 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 agoMaybe 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).
- znpy 6y agoAll 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 time. Even xterm, with the right fonts, it's a very nice setup. I almost can't see the difference between a gtk emacs window and an emacs session running in xterm-unicode with proper fonts and antialiasing. Xorg might not be "optimal", but it works very well for me and I won't be switching to anything else until a wayland or whatever reach feature parity (including but not limited to network transparency). Whatever,
- bitwize 6y ago> All these Xorg/X11 problems people complain about... I honestly don't see them. 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.
- pjmlp 6y agoOne wouldn't notice that, given how many eschew the progress made and live in the command line as if stuck in the 80's.
- enriquto 6y agoIt's not as much "the command line", but being able to talk to your computer using a human-like language, instead of pointing with your finger like a baby or a monkey. Do you know any computer/user interface that is based on writing what you want to do? (instead of selecting it from a small list of possibilities) The only one that I know is the "primitive" command line.
- pjmlp 6y agoYes, the REPL as used at Xerox PARC, while Bell Labs was busy with troff.
- tpoacher 6y agoAm I the only person who likes "prehistoric x-apps"? E.g. xdiskusage is far better than any other disk usage app I've tried.
- aduros 6y agoProud xeyes user here. Have you tried duc for disk usage? It's minimal and has a nice visualizer.
- tpoacher 6y agoI did ... but tbh can't remember what my beef was with it now, I just remember that when I compared them all it wasn't a favourite, hahah ... I settled on xdiskusage and gt5 (the latter when I'm on a terminal). Both great tools.
- deleted 6y ago[deleted]
- kesor 6y ago... if only xterm would support ligatures and colored emojis :)
- enriquto 6y agoAlright for font ligatures, but I hope that if they ever support colored emojis those are disabled by default.
- souprock 6y agoMost terminal emulators won't support the -S option. That is needed so that another program can feed data into an xterm that has been created as a child process. I've seen it used for a modem dial-up program and I've seen it used for the emulation of old computers with serial consoles. It would probably find use with debuggers. Sometimes you just want to pop open a new window, and xterm is the only terminal emulator that will cooperate. The option parsing is buggy. Only file descriptor 0 works, but that is good enough because of the dup2 system call. Fork, set up the file descriptors, and then exec an xterm like so: xterm -S/0 -T foo -n foo -name foo I'd love to get the feature, with the exact same syntax, into all the terminal emulators. That would mean that x-terminal-emulator, which is a link to whatever the user installed, would always have the feature.
- brobdingnagians 6y agoI started using st from suckless and realized that met most of my needs, especially when I learned to use tmux properly. In some ways XTerm is the luxury version compared to st. I don't necessarily recommend st, but it is always interesting to learn that you can get by with a lot less than you thought you could. And it helps you learn some tricks you might not otherwise think you needed.
- checkyoursudo 6y agoI use st as well. Honestly, the main reason is that I can configure it to use ligatures, whereas the few that offer ligature support aren't terminals that I prefer, and the terminals I like better don't offer ligature support. So, st it is. Otherwise, it's not the best with regard to overall capabilities (though that is because of my limited ability to write my own original patches for it, I suppose), but it's not the worst either. I don't especially recommend it either, but I like it a lot for my own use. People who don't know how to patch C on Linux are probably not really going to want to use it with the default config.
- rcarmo 6y agoThis is gold. I think that with a few extra tweaks (sane scroll bars and the like) it might replace rxvt as my regular “lite” terminal.
- unhammer 6y agoI use sakura, since it has great support for unicode (presumably through libvte, which also xfce4-terminal uses). See e.g. https://i.imgur.com/G6arkK9.png https://i.imgur.com/G6arkK9.png using some extracts from http://www.madore.org/~david/misc/unitest/ http://www.madore.org/~david/misc/unitest/ - xterm just gives up (tried uxterm as well as the .Xresources settings here) - st prints the arabic backwards (left to right, which I suppose you might prefer if you don't actually plan on reading it), has no colour on the emoji (which again you might prefer!), and completely fails to display the double-composed diacritics (this is a bad one, even if you prefer to KISS) - I don't know what kitty is doing with the arabic, all I see are some strange rendering artifacts - sakura (and xfce4-terminal) passes all the tests
- harrygeez 6y agoI stopped using xterm because C-h and C-; bindings doesn't work on Emacs. I'm not sure if there's a way to configure it to make them work but I remember trying to look for such settings and gave up. It's easier to just use urxvt.
- harrygeez 6y agoI have an old laptop that I use to play with Linux and run my home server. It has an not so mainstream ATI integrated GPU and I had a difficult time configuring compton (with i3) to just look good and perform well. With wayland and latest mesa everything just works and is very snappy. It's not perfect though whenever I reboot my machine I have to put my display to sleep first just to make the display work (just shows a blank screen otherwise) but that's a problem with mesa though and nothing to do with wayland.
- miccah 6y ago> but we can hijack it to instead scan the screen for URLs and open the browser For comparison, rxvt-unicode has perl utils for mouse-less URL selection [1]. Since it's operating within the terminal, scrollback is also available for selection (not just the currently visible screen). After invoking the selection mode, it's as easy as using j/k to choose the URL and Enter to open or y to yank to clipboard. Installed on Arch with the `urxvt-perls` package. [1] https://github.com/johntyree/urxvt-perls https://github.com/johntyree/urxvt-perls
- jstimpfle 6y agoxterm is still the only usable terminal that supports crisp (bitmap) fonts as far as I'm aware. Which is why I'll be using it until we have high DPI screens everywhere. All the other terminals are unbelievable blurry with their antialiased fonts on ~100dpi screens. (Or alternatively, unbelievably ugly, when turning off antialiasing). I never understood why so few people are bothered. These blurry fonts hurt my eyes.