|
From: | GNU bug Tracking System |
Subject: | bug#62233: closed (Using Emacs Lisp) |
Date: | Tue, 12 Sep 2023 00:19:02 +0000 |
Your message dated Mon, 11 Sep 2023 17:17:56 -0700 with message-id <CADwFkmmJN5YouUh-YZEWU=HNS6a+FUFwkv5uHK2vhB5zEpCgQw@mail.gmail.com> and subject line Re: bug#62233: Using Emacs Lisp has caused the debbugs.gnu.org bug report #62233, regarding Using Emacs Lisp to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 62233: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62233 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: Using Emacs Lisp Date: Fri, 17 Mar 2023 07:26:35 +0000 (UTC) Hi FSF,I was wondering if the FSF can turn Emacs Lisp into a tool that is as easy to use as two of these mainstream Lisp environments - Allegro Common Lisp and LispWorks. And to do away with difficult to remember commands such as C-x C-m for example, if there is such a thing.Otherwise, its a free and useful tool for learning Lisp and using it for AI.That's all I have to say.--- Andrew Goh
--- End Message ---
--- Begin Message ---Subject: Re: bug#62233: Using Emacs Lisp Date: Mon, 11 Sep 2023 17:17:56 -0700 Andrew Goh <andrewgoh95@yahoo.com.sg> writes: > Hi FSF, > > I was wondering if the FSF can turn Emacs Lisp into a tool that is as > easy to use as two of these mainstream Lisp environments - Allegro > Common Lisp and LispWorks. And to do away with difficult to remember > commands such as C-x C-m for example, if there is such a thing. > > Otherwise, its a free and useful tool for learning Lisp and using it > for AI. > > That's all I have to say. Thanks for your feedback. We are continuously working on making Emacs Lisp easier to use. I don't think we can simplify commands much though, but we trying when we can. Emacs is an old piece of software, which means that some of the conventions we follow may seem outdated. However, many users use and depend on them, and it wouldn't be fair to them to just throw out all those conventions out in one go. We therefore improve them incrementally, and sometimes it's slow going. I don't see anything actionable here, so I'm closing the bug report.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |