1,582 karma · joined August 4, 2009
The v3 chathistory support and the always-on[1] multi-client[2] features paired with modern clients (like Goguma) go a long way at providing a modern chat environment. Most others on the server don't even know that they are using IRC.
The built-in websocket support is another key feature for me since it lets me to provide a web client just by serving some static files (I use Gamja for this).
[1] always-on: https://github.com/ergochat/ergo/blob/master/docs/USERGUIDE....
[2] multiclient: https://github.com/ergochat/ergo/blob/master/docs/USERGUIDE....
Yes but with only one real server which has 99%+ of the users and the rest on single user Leafnode instances.
Regular people almost never used those words. Only the media did.
Long line handling has greatly improved in emacs-29. Multi-megabyte lines are not a problem anymore.
How-to play video: https://www.youtube.com/watch?v=zfXPIhvFPjw
Space-Biff review: https://spacebiff.com/2024/09/25/ghq/
I do too. And the underlying shr rendering library is invaluable when so much of email traffic is text/html. A bunch of other stuff like mastodon.el and devdoc.el rely on it too.
> It is getting increasingly difficult to use;
In my experience it's not that much worse than it was 10 years ago. By the time eww came about the JS-less browsing ship has long sailed. The sort of stuff that was working back then still tends to work now. We lost some good sites like the BBC text-only mode but also gained some nice text proxies like 68k.news and brutalist.report.
https://xapian.org/history https://sigir.org/files/forum/S2000/MUSCAT_note.pdf
It's been trouble free and very performant, a real workhorse.
Yep, found it: https://www.ibiblio.org/pub/historic-linux/ftp-archives/suns...
And the Linux kernel CREDITS file has an entry mentioning it too:
N: Rick Sladkey
D: utility hacker: Emacs, NFS server, mount, kmem-ps, UPS debugger, strace, GDB
[...] bind -n S-PPage copy-mode -u
bind -T copy-mode S-PPage send -X page-up
bind -T copy-mode S-NPage send -X page-down
The first line is a top-level binding to enter copy-mode and immediately scroll up one page. The other two add bindings within copy-mode so you can continue to scroll up or down with those keys.I also have a small hack in my .zshrc to start scrolling up with `M-v` (like in Emacs) while at a shell prompt:
tmuxup(){tmux copy-mode -u}
zle -N tmuxup
bindkey '^[v' tmuxupBoth are doable with modern servers and clients thanks to v3 chathistory. Ergo (server) and Goguma (mobile client) in particular make this work very nicely.
Mozilla Suite rather than Netscape Navigator. This is from 2000 which was well into the Mozilla era and I don't think that Netscape bugs made it into Bugzilla anyway.
With Go on Linux libc is only needed when the libc DNS resolver is used (instead of Go's built-in one) or if C libraries are used. superfile doesn't need either of these so it's very simple to build it as a pure Go executable which will be statically linked and contain no C code at all.
> What's worse is that you can't even really statically link it without herculean effort.
The program we are discussing happens to be written in Go so it's trivial to build a statically linked executable.
Emacs is the one program I know of that can actually do this. It can pop up frames (Emacs lingo for windows) on multiple displays at the same time and even mix tty and X11 frames. The Emacs session survives connection loss fine, frames on other displays continue working and you can reconnect if desired.
The one caveat is that Gtk used to have a bug that caused it to uncontrollably abort on connection loss but I build my Emacs with --without-x-toolkit (so it uses raw xlib, no toolkit) and that configuration has always been robust and performant. If I remember correctly the Gtk bug might be fixed now too.
(Talking about native implementations here not xlib bindings).