Path: gmdzi!unido!mcsun!uunet!ukma!wuarchive!zaphod.mps.ohio-state.edu! magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!unreplyable!garbage From: r...@GNU.AI.MIT.EDU (Richard Stallman) Newsgroups: gnu.emacs.help,comp.emacs Subject: Emacs 19 Message-ID: <9103220009.AA06473@mole.gnu.ai.mit.edu> Date: 22 Mar 91 00:09:17 GMT Sender: dae...@tut.cis.ohio-state.edu Followup-To: gnu.emacs.help Organization: Gatewayed from the GNU Project mailing list help-gnu-em...@prep.ai.mit.edu Lines: 10 I have not worked on Emacs 19 myself since almost two years ago; I haven't had time. Unfortunately, there has been turnover in the people working on it. Dealing with Unipress's threats set things back a few months also. Projects slip, and it's not much use berating people for the speed of their progress. At least there is steady progress now. I was certainly mistaken when I predicted when Emacs 19 would be available. But I can't unsend that message now. All I can do is admit that it turned out to be wrong.
Path: gmdzi!unido!mcsun!uunet!ukma!wuarchive!zaphod.mps.ohio-state.edu! magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!unreplyable!garbage From: j...@LUCID.COM (Joseph Arceneaux) Newsgroups: gnu.emacs.help,comp.emacs Subject: Emacs 19 Message-ID: <9103220058.AA01562@hugo> Date: 22 Mar 91 00:58:37 GMT Sender: dae...@tut.cis.ohio-state.edu Reply-To: j...@gnu.ai.mit.edu Followup-To: gnu.emacs.help Organization: Gatewayed from the GNU Project mailing list help-gnu-em...@prep.ai.mit.edu Lines: 14 Things which have delayed version 19 include changes in personnel, leaves of abscence, the Unipress threats, and an iterative process of trying and then throwing out some features. Feedback from Epoch users was involved in this last, and has, positively I believe, influenced aspects of version 19. The 1988 message about release in "6 to 9 months" was long before I began work on 19, so such an early version would have been missing some features that many users would like, such as working under X11. It is certainly regrettable to have made any promises about release dates, and as far as I am concerned I can only attribute this to my weakness before severe insistence from various groups of users. Rather than make such an error again, I will go back to work.