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: Tue, 26 Nov 2024 18:58:37 -0300 [thread overview]
Message-ID: <CADs++6ii=Q_uWWWzTzCcuSHmehhXx+PjmH=KXOGCU65007nE4A@mail.gmail.com> (raw)
In-Reply-To: <a4550504-e10b-4a80-8bcf-7122e038136b@me.com>
On Mon, 25 Nov 2024 at 14:59, Raj Divecha via Bug reports for GNU
Emacs, the Swiss army knife of text editors <bug-gnu-emacs@gnu.org>
wrote:
>
> I wish I could contribute but unfortunately I am stuck with my bread
> & butter job. I am a seasoned systems engineer and mostly work on
> C/C++/Python, validating features of various ICs that my company
> manufactures and I know if I want I can work on this non-trivial
> change but at the end of the day my bread & butter job takes
> priority over everything else.
>
> Just out of curiosity, what will it take to get this done? Is there
> a document I can review and get a feel for the amount of work? And
> approximately, how many engineers do you think are needed to work on
> this and the different expertise required? LISP is kind of dead and
> the users might need Python to customize their interface, thus, I
> believe both LISP and Python will have to be supported
> simultaneously.
Hi Raj,
have you read this thread?
https://lists.gnu.org/archive/html/emacs-devel/2024-10/msg00018.html
https://lists.gnu.org/archive/html/emacs-devel/2024-10/threads.html#00018
Cheers,
Eduardo Ochs
next prev parent reply other threads:[~2024-11-26 21:58 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 [this message]
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
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++6ii=Q_uWWWzTzCcuSHmehhXx+PjmH=KXOGCU65007nE4A@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).