|WikiProject Computing / Software||(Rated C-class, Low-importance)|
fork in the first line
The Mac OS X article does not have BSD in the first line, and Windows does not have OS/2 in the first line. So I think having a large section dedicated to the split between the GNU project and the XEmacs hackers is quite enough. This article needs to be a description of XEmacs not just another article about GNU Emacs.
- Please sign your posts. A much lower percentage of Mac OS X and Windows are BSD and OS/2, so these cases are not analogous. Gronky 15:43, 17 April 2007 (UTC)
- Do you have proof for that, XEmacs and GNU Emacs went their separate ways 15 years ago. While OS X imports code from Free/Open Source all the time. 188.8.131.52 21:18, 17 April 2007 (UTC)
The article mentions the fork issue throughout the article, so it should probably be quickly mentioned in the summary, no? The XEmacs Web site mentions it at <http://xemacs.org/About/>. They've hardly "went their separate ways 15 years ago". My understanding is there is lots of synchronization of source code between projects. According to the XEmacs maintainers:
- Almost all features of GNU Emacs are supported in XEmacs. The maintainers of XEmacs actively track changes to GNU Emacs while also working to add new features.
--184.108.40.206 12:52, 19 April 2007 (UTC)
- Okay fair enough on mentioning the fork in the title as long as we do not go back to having a whole article about politics with no description of the software itself Zeth 01:01, 25 April 2007 (UTC)
A fork and yet not a fork
Note the history does not match up to the rhetorical use of XEmacs as an example of a fork, so it is best not to overegg it as a canonical example of a fork. The modern GNU Emacs and XEmacs were both forks in one sense, both were based on the unreleased version of Emacs version 19 but both deliberately differed from it. When species A mutates, you now have B and C (rather than A and B).
I have attempted to make the page more positively about Xemacs, (rather than just talk about the split with GNU Emacs), as well as add references. Some changes have been reversed, which is fine, but can those judging, please try and make things better, rather than just revert changes for the sake of it. Again, this is not an article about GNU Emacs, it is an article about XEmacs, so while mentioning the fork, the rest does not have to just be about GNU Emacs. We want to know about the features and the over a decade and a half since then. Note also I am not just trying to pimp XEmacs, I am actually a GNU Emacs user.
Issues concerning much older versions of this page
The page has been rewritten recently, so the issues below do not apply but are kept for historical reasons.
- "Since both emacsen share the same license, code can be transplanted back and forth between them"
You forgot to add "... but because FSF want to have copyright assignments for all of GNU Emacs code they can't just take code from XEmacs". --Taw
- Done. --CYD
- "Inline images are available without tricks."
Could someone clarify this statement? As far as I can see, inline images work fine in Emacs 21, without any hackery. --CYD
- If the statement does no longer apply, feel free to fix it. IIRC Emacs 20 was not able to display images inline without some clever kludgery. ----Robbe
Can anything objective be said about the pros and cons of GNU Emacs vs. Xemacs in their native Win 95/98/ME implementations? (Ditto Win NT/2000/XP implementations). I think many stuck on Windows, but eager to give Common Lisp a try, find deciding between the two emacsen as difficult as learning the emacs way. --Anonymous
- If you want to give common lisp a try then download clisp for windows. Emacs Lisp is not a full featured implementation of common lisp. I run XEmacs on Windows simply because I prefer the XEmacs philosophy of open source as opposed to Stallman's... XEmacs has a few features I like which haven't yet made it into the GNU Emacs native windows port (Please don't encourage me to run Cygwin)
- Inline Images (images in buffers)
- Automatic Package management
- extents (buffer regions with specific properties)
- Proper dialog boxes (dialog boxes only appear when interacting with the GUI naturally)
- buffer tabs (similar to other MDI environments, if you like that)
- more customizable options available in the menubars (I hate trawling the customize buffers to that one elusive option :-) )
- I encourage someone to counter this list with things that GNU Emacs for Win provides, and maybe if there's a useful set of arguments for each editor they could be merged into the article. Stu Hacking talk 14:53, 6 September 2007 (UTC)
- Do we need any of this? I think these particular version names show something of the irreverent character of XEmacs, in contrast with More Sensible Emacs. The 21.5 vegetable series is less interesting. --Anonymous
good documentation or not
- "In the past, some detractors have complained that because of its more aggressive, features-driven approach, XEmacs internals are less consistent and less extensively documented than GNU Emacs. Actually, the opposite is true: XEmacs comes with a 140-page internals manual (Wing and Buchholz, 1997), making it one of the most well-documented software projects, and has been more open to change than GNU Emacs, with the result that its internals have been extensively rewritten to improve consistency and follow modern programming conventions stressing data abstraction."
Well does it have good documentation or not? Why does the article say it has poor documentation then contradict itself the next sentence and say it has good documentation? --220.127.116.11 18:51, 27 November 2005 (UTC)
I've always thought the X stood for "extended" or "extendable", contrary to the more intuitive guess that it comes from the X window system. I see this article currently says it does come from the X window system. Is this correct, or just an incorrect, though intuitive, guess?
- The article is wrong. It started life as Lucid Emacs. Lucid went bust and other companies wanted to carry on shipping Lucid Emacs. However, using the trademark was legally ambiguous because no one knew who would control the trademark after the dust settled. So X is for brand X, nothing to do with X Windows or X.org.
New logo proposal!
(Yea, it's a joke and shows a rather sick sense of humor.) 18.104.22.168 (talk) 21:31, 21 March 2010 (UTC)