unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Raj Divecha via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: 74488@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#74488: Why not modernize Emacs
Date: Wed, 27 Nov 2024 21:02:11 +0000 (UTC)	[thread overview]
Message-ID: <ca288a33-6815-4bf5-965f-84f357b491c1@me.com> (raw)
In-Reply-To: <CADs++6iJNEqMJOOa4tWq1jx+51nS1J5vg=xMb0wv6_z9B_YA4A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]

Regarding Lisp & Python : I suggested Python as an alternative. No seasoned programmer is concerned about which programming language to use. Thus. Lisp only is also just fine. And, IMO, supporting Python is probably not going to be difficult because it would be a wrapper over the Lisp code. At the basic level there needs to be a well defined object model, which Emacs already has and the same can be replicated in Python. Once done, a converter app will be needed to duplicate Lisp methods in to the Python modules. These methods will simple execute the underlying Lisp code (somehow), thus wrappers. This should provide python support. I could be wrong but it is just an idea I could think of. "Most people who write Emacs extensions do that in their spare time, and for fun" - I wasn't referring to extensions but the core of Emacs. Oh well, I believe I have troubled you guys enough. If possible, I will spend some time some day(s) and familiarize my self with Emacs and maybe in the process create a simple step-by-step process to get others started as well. Those n hour-long David Wilson videos only scare away people more than before they come by those videos! Richard Stallman's email was found in my junk folder but I found it never the less. Happy Thanksgiving to all who celebrate it and for the rest, keep having fun with Emacs! --*-- END OF THIS THREAD --*-- On Nov 26, 2024, at 9:08 PM, Eduardo Ochs <eduardoochs@gmail.com> wrote: On Tue, 26 Nov 2024 at 19:42, Raj Divecha <rjd1977tech@icloud.com> wrote: But the point is why not just make a user friendly interface? How can a new comer like VS Code come and grab the market and a powerful tool like Emacs can't? Hi Raj, Most people who write Emacs extensions do that in their spare time, and for fun - and writing for a target audience of users who know the basics of Lisp is much more fun that writing for users who don't know Lisp, who don't like Lisp, and who want an editor that is like VSCode... Cheers =(, Eduardo Ochs http://anggtwu.net/eev-intros/find-elisp-intro.html -- They tried to fool a Black population By telling them Lisp-Lisp dead And I knows Lisp no dead

[-- Attachment #2.1: Type: text/html, Size: 3029 bytes --]

  reply	other threads:[~2024-11-27 21:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22 23:27 bug#74488: Why not modernize Emacs Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23  3:57 ` Stefan Kangas
2024-11-24  4:37   ` Richard Stallman
2024-11-23  6:59 ` Eli Zaretskii
2024-11-25 17:58   ` Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-25 18:59     ` Eli Zaretskii
2024-11-26 21:58     ` Eduardo Ochs
2024-11-26 22:42       ` Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-27  4:07         ` Eduardo Ochs
2024-11-27 21:02           ` Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-28  4:52     ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=ca288a33-6815-4bf5-965f-84f357b491c1@me.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74488@debbugs.gnu.org \
    --cc=eduardoochs@gmail.com \
    --cc=eliz@gnu.org \
    --cc=rjd1977tech@icloud.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).