all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Andrew Goh <andrewgoh95@yahoo.com.sg>
Cc: 62233@debbugs.gnu.org
Subject: bug#62233: Using Emacs Lisp
Date: Fri, 17 Mar 2023 08:13:32 +0000	[thread overview]
Message-ID: <87sfe3lrrn.fsf@posteo.net> (raw)
In-Reply-To: <933663386.985655.1679037995911@mail.yahoo.com> (Andrew Goh's message of "Fri, 17 Mar 2023 07:26:35 +0000 (UTC)")

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.
> --- Andrew Goh

You can already write Emacs Lisp code using Nano or vi and run the code
using "emacs --script".  The discussion to abandon the Emacs UI comes up
from time to time and is usually fruitless.  There are a lot of people
who are used to and like keychords and a lot of packages rely on them,
so it would not be worth betraying them.  There are people who write
scripts that make Emacs emulate different kinds of editors.  I believe
that would be the best way forwards for what you are looking to do.

Also, I believe you wanted to address GNU, specifically the Emacs maintainers.

-- 
Philip Kaludercic





  reply	other threads:[~2023-03-17  8:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <933663386.985655.1679037995911.ref@mail.yahoo.com>
2023-03-17  7:26 ` bug#62233: Using Emacs Lisp Andrew Goh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17  8:13   ` Philip Kaludercic [this message]
2023-03-18  3:42     ` Jean Louis
2023-03-18  7:39       ` Philip Kaludercic
2023-03-18  3:46   ` Jean Louis
2023-09-12  0:17   ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfe3lrrn.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=62233@debbugs.gnu.org \
    --cc=andrewgoh95@yahoo.com.sg \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.