2 ms·
Will I still be able to compile Emacs to use X and libXaw3D for the foreseeable future? Or is this some "modernization" effort to break what's old and works and
by bitwize 6y ago
Will I still be able to compile Emacs to use X and libXaw3D for the foreseeable future? Or is this some "modernization" effort to break what's old and works and force everybody onto GNOME's new hotness?
- jhasse 6y agoEmacs is open source. You will always be able to do that. No one forces you to `git pull`.
- hjek 6y ago> Emacs is open source. I think the person you reply to is aware of that but is asking whether it's still available in upstream. > You will always be able to do that. There's a difference between the functionality existing and having to implement it yourself. It's unlikely to be trivial to do so even if it's open source, so your response is not helpful to answering the question.
- jhasse 6y ago> There's a difference between the functionality existing and having to implement it yourself. Well, the functionality (use X and libXaw3D) exists, he doesn't have to implement it himself.
- froh 6y agoIf I'm reading the article right, it's not as wayland or gnome specific fix, but a fix at the proper x11 level, generic and independent of the toolkit. That's referenced by the "(and More)".
- bitwize 6y agoYeah, I saw that they implemented a new GTK/Cairo "terminal" backend. This is a good approach and helps to further decouple Emacs's editor core bits from its rendering bits.