Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove support for XEmacs #11

Open
ghost opened this issue Jul 29, 2015 · 4 comments
Open

Remove support for XEmacs #11

ghost opened this issue Jul 29, 2015 · 4 comments
Assignees

Comments

@ghost
Copy link

ghost commented Jul 29, 2015

Maintaining dual compatibility with Emacs and XEmacs is onerous. With the last official XEmacs release in 2009 with an associated remnant user base and given the reinvigoration of Emacs itself XEmacs support should be removed. Doing so removes substantial conditionally twice written logic and code that eases code maintenance and improvements moving forward.

Consider this issue at this time as survey / poll status.

@alexott
Copy link
Contributor

alexott commented Jul 29, 2015

Agree! We may also need to look what Emacs versions will be supported to be able to use new features

@ware
Copy link
Contributor

ware commented Jan 2, 2016

I've made a request on the mail list for people to register their thoughts in this issue.

@ware ware self-assigned this Jan 2, 2016
@myrkraverk
Copy link

I come from the mailing list. I use XEmacs 21.4.

That said, I don't have strong feelings about ECB and XEmacs. If you want to drop it, drop it. On the other hand, I may be persuaded to help with the XEmacs support if you decide to keep it.

@tbcs
Copy link

tbcs commented Aug 1, 2016

I share the concerns regarding the additional effort for maintaining compatibility. I was curious to see how much compat code actually is inside ECB, so I did an experiment. After removing all XEmacs related code ECB's size was reduced by about 5%. IMHO this is a significant reduction, given that ECB currently consists of roughly 38 KLOC.

Is there interest in going forward with removing the compat code? Let me know if I should open a pull request. Right now the compat code removal consists of a single, large, squashed commit, but I could break it down into separate steps if necessary.

Side note: xemacs.org is currently offline (and apparently has been for at least 2 weeks).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants