unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Raj Divecha <rjd1977tech@icloud.com>
Cc: 74488@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#74488: Why not modernize Emacs
Date: Wed, 27 Nov 2024 01:07:57 -0300	[thread overview]
Message-ID: <CADs++6iJNEqMJOOa4tWq1jx+51nS1J5vg=xMb0wv6_z9B_YA4A@mail.gmail.com> (raw)
In-Reply-To: <d4687bda-3011-4fc1-bf37-2391067caae8@me.com>

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





  reply	other threads:[~2024-11-27  4:07 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 [this message]
2024-11-27 21:02           ` Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CADs++6iJNEqMJOOa4tWq1jx+51nS1J5vg=xMb0wv6_z9B_YA4A@mail.gmail.com' \
    --to=eduardoochs@gmail.com \
    --cc=74488@debbugs.gnu.org \
    --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).