XEmacs support will be discontinued for new Tramp versions
"Stephen J. Turnbull" <[email protected]> Wed, 30 Dec 2015 13:15:04 +0900
| Newsgroups | gmane.emacs.xemacs.beta |
|---|---|
| Message-ID | <[email protected]> |
Michael Albinus writes: > I have just merged the new Tramp 2.2.13 into the XEmacs package > repository. This will be the last Tramp version with XEmacs > support. Thank you for all your support over the years! > The reason is, that there is no benefit to keep this compatibility in > Tramp. Of course there is. Major new features that depend on packages like dbus.el won't work in XEmacs, but bug fixes and many pure-Lisp improvements will, I'm sure. For example, the recent Mac OS X issue (Mac OS X has a hard limit on the length of a named pipe or Unix domain socket name, or maybe just the latter) was addressed much more recently than 10 years ago. Heck, Apple didn't invent it until a couple years ago. :-) It's up to you whether the possibility that you will address issues (heck, after the Bash envvar hack, I wouldn't bet that there aren't bugs in TRAMP from 1999! ;-) that affect XEmacs users is worth the effort to keep an "XEmacs clean" code base, but it's not "no benefit." You also seem to be unaware of some of the syncs that have taken place in XEmacs 21.5 (which is the recommended version for users who are willing to report bugs, and don't insist on near bulletproofness): > All new features which have arrived in Tramp over the last 10 years > are almost useless in XEmacs, because some of the underlying magic > file name operations do not exist in XEmacs (for example > process-file, start-file-process), start-file-process is implemented in 21.5. I'm not sure how far SXEmacs has progressed on such syncs. > or because needed GNU Emacs packages are not available for XEmaxs > (for example, dbus.el). Most of XEmacs users won't notice this > stopped support, I guess. > I'm willing to support Tramp 2.2.13 in the XEmacs repository in case of > serious problems. That sounds like a reasonable compromise to me. I hope the bug in Mac OS X I mentioned above would qualify as "serious"?