Oh, thanks for explaining that! So, new Virtual-T patches should be sent to the majick repository on codeberg from which they'll eventually filter into the official sf.net repository? I was thinking it shouldn't be too tricky to enable the server automatically if one uses -nogui and, if I remember correctly, the need to use /dev/null stuff is pretty easy to fix by catching SIGTSTP.
—b9 P.S. I'd never have found your repository without the direct link. Is that intentional? Google is now informing me that, *“Majick Virtual-T is a specific magic routine frequently associated with performances conducted over platforms like Zoom, Skype, or FaceTime.”* Adding more specific keywords directs me to GitHub <https://github.com/McNeight/VirtualT>, which always ranks highly in search engines. (GitHub, you were supposed to destroy the Sith, not join them!) On Tue, Dec 23, 2025 at 4:17 PM Joshua O'Keefe <[email protected]> wrote: > On Dec 23, 2025, at 9:27 AM, B 9 <[email protected]> wrote: > > How does your repository differ from the one at sf.net/p/virtualt? > > > There are a handful of little fixes floating around that haven't made it > upstream in the 4 years since Ken checked something in. Overall, the idea > is to accumulate stuff that Ken doesn't have time to bring in upstream just > yet. So far I've got: > > majick dbcae5e81a Ken's fix for remote socket 17 hours ago > majick 7f26c3208f Bump version 1.8.1-majick last year > majick 44800d23da Fix 20 year old graphical bug (per kpetitt) last year > majick 2ad48bca7a Fix for modern compilers. Fix Linux build. 1.8-manyfixes > last > year > majick 30b8689a5c Backport cosmetic changes from the devterm fork last > year > majick db0a4c4f96 Make Darwin build not static last year > majick ab57317db0 Fix darwin build for modern OS last year > > None of these things are especially mandatory, although I had to make some > changes to get both the macOS and Linux/amd64 build at some point last year > (mostly fixes like an extern being declared in a way it didn't like, > redeclaration in a c file, and building it -fPIC so it didn't core dump, > and there's no such thing as a fully static binary on macOS.) > > The only commit that's a major change is ab57317db0, which makes the > keyboard actually functional on macOS. > > As far as I'm aware other than the Darwin commits, everything else should > be cherry-pickable for folks who need them. Also, please note that I've > moved all work to codeberg and have archived all of my GitHub repos. What I > have is at https://codeberg.org/majick/virtualt-code > > >
