* bug#62233: Using Emacs Lisp
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
2023-03-18 3:42 ` Jean Louis
2023-03-18 3:46 ` Jean Louis
2023-09-12 0:17 ` Stefan Kangas
2 siblings, 1 reply; 6+ messages in thread
From: Philip Kaludercic @ 2023-03-17 8:13 UTC (permalink / raw)
To: Andrew Goh; +Cc: 62233
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#62233: Using Emacs Lisp
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
@ 2023-03-18 3:46 ` Jean Louis
2023-09-12 0:17 ` Stefan Kangas
2 siblings, 0 replies; 6+ messages in thread
From: Jean Louis @ 2023-03-18 3:46 UTC (permalink / raw)
To: Andrew Goh; +Cc: 62233
* Andrew Goh via "Bug reports for GNU Emacs, the Swiss army knife of text editors <bug-gnu-emacs@gnu.org> [2023-03-17 10:29]:
> I was wondering if the FSF can turn Emacs Lisp into a tool that is
> as easy to use as two of
Thanks.
Can you tell what it means "as easy to use"? Can you describe what
makes it easy?
> these mainstream Lisp environments - Allegro Common Lisp and
> LispWorks.
They may be "main" in proprietary world, where commercial companies
dictate over their users, while in free software world, they can't
compare. I guess that SBLC could be the main free software Common Lisp
implementation.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#62233: Using Emacs Lisp
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
2023-03-18 3:46 ` Jean Louis
@ 2023-09-12 0:17 ` Stefan Kangas
2 siblings, 0 replies; 6+ messages in thread
From: Stefan Kangas @ 2023-09-12 0:17 UTC (permalink / raw)
To: Andrew Goh; +Cc: 62233-done
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.
^ permalink raw reply [flat|nested] 6+ messages in thread