* bug#74488: Why not modernize Emacs
@ 2024-11-22 23:27 Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23 3:57 ` Stefan Kangas
2024-11-23 6:59 ` Eli Zaretskii
0 siblings, 2 replies; 3+ messages in thread
From: Raj Divecha via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2024-11-22 23:27 UTC (permalink / raw)
To: 74488
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
Hi, I am an occasional Emacs user. I know that Emacs is a very capable editor. In fact, most modern editors provide similar features, just that the learning curve for them is close to nothing. They simply work out of the box. Thus, I am wondering, why not Emacs? How difficult would it be to provide a different interface, a simpler one yet fully capable? For example, while I can use Emacs for simple text editing, I still can't use it as my developer IDE. I want some feature that will help me easily install a project explorer like extension. The project explorer could help create workspaces, project, help me navigate them with ease etc. Think MS's VS Code. On the same lines, I would like a LaTeX window with its own extensions. Emacs already supports all this but the learning curve is so steep that I don't feel like opening it anymore! Thus wondering why can't Emacs come out with a simpler interface (and allow one to switch to an advance interface when needed) and throw the learning curve out the window? -OR- Am I missing something? Thanks, Raj
[-- Attachment #2.1: Type: text/html, Size: 1243 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#74488: Why not modernize Emacs
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-23 6:59 ` Eli Zaretskii
1 sibling, 0 replies; 3+ messages in thread
From: Stefan Kangas @ 2024-11-23 3:57 UTC (permalink / raw)
To: Raj Divecha, 74488
tags 74488 + notabug
close 74488
thanks
Raj Divecha via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> Hi, I am an occasional Emacs user. I know that Emacs is a very capable
> editor. In fact, most modern editors provide similar features, just
> that the learning curve for them is close to nothing. They simply work
> out of the box. Thus, I am wondering, why not Emacs? How difficult
> would it be to provide a different interface, a simpler one yet fully
> capable? For example, while I can use Emacs for simple text editing, I
> still can't use it as my developer IDE. I want some feature that will
> help me easily install a project explorer like extension. The project
> explorer could help create workspaces, project, help me navigate them
> with ease etc. Think MS's VS Code. On the same lines, I would like a
> LaTeX window with its own extensions. Emacs already supports all this
> but the learning curve is so steep that I don't feel like opening it
> anymore! Thus wondering why can't Emacs come out with a simpler
> interface (and allow one to switch to an advance interface when
> needed) and throw the learning curve out the window? -OR- Am I missing
> something? Thanks, Raj
Thanks for sharing your ideas about how to improve Emacs.
We always aim for at least feature parity with typical IDEs, and in many
cases we actually have a much stronger set of features than they do.
But it is true that the Emacs interface is fundamentally different from
that of VSCode. It's challenging to provide a different user interface
along the lines that you suggest, while also providing all the features
that we do.
However, this bug list is not really appropriate or intended for very
wide-ranging discussions about what Emacs could look like in the future.
It is intended for much more focused discussions about specific and
reproducible bugs in Emacs, and narrowly scoped feature requests. For
that reason, I will close this bug report now.
I believe you might have more success discussing these and other similar
ideas in forums such as the Emacs Reddit page or on IRC. Thanks.
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#74488: Why not modernize Emacs
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-23 6:59 ` Eli Zaretskii
1 sibling, 0 replies; 3+ messages in thread
From: Eli Zaretskii @ 2024-11-23 6:59 UTC (permalink / raw)
To: Raj Divecha; +Cc: 74488
severity 74488 wishlist
thanks
> Date: Fri, 22 Nov 2024 23:27:09 +0000 (UTC)
> From: Raj Divecha via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Hi, I am an occasional Emacs user. I know that Emacs is a very capable editor. In fact, most modern editors provide similar features, just that the learning curve for them is close to nothing. They simply work out of the box. Thus, I am wondering, why not Emacs? How difficult would it be to provide a different interface, a simpler one yet fully capable? For example, while I can use Emacs for simple text editing, I still can't use it as my developer IDE. I want some feature that will help me easily install a project explorer like extension. The project explorer could help create workspaces, project, help me navigate them with ease etc. Think MS's VS Code. On the same lines, I would like a LaTeX window with its own extensions. Emacs already supports all this but the learning curve is so steep that I don't feel like opening it anymore! Thus wondering why can't Emacs come out with a simpler interface (and allow one to switch to an advance interface when needed) and throw the learning curve out the window? -OR- Am I missing something? Thanks, Raj
The simple answer to your questions is "because no one has yet
proposed code changes to implement those features."
Emacs is developed by a loosely-coupled group of volunteers, each one
of whom contributes changes in the areas that are of interest to
him/her and match their domains of expertise. We acknowledge the need
and the advantages of having the advanced IDE-related features work
out of the box, but have no way of assigning someone to the job of
actually doing that non-trivial job. It is non-trivial because
different users of Emacs have different interests and needs (e.g.,
develop in vastly different programming languages), and setting up the
tools we have to fit the needs of a particular user is a complex task.
In addition, unlike VS Code, we don't want to promote non-free servers
and services, so it is much more difficult for us to provide OOTB
configuration for features that rely on external programs and servers.
But if and when someone comes with code that does one of these jobs,
we embrace that very quickly. Examples include Tree-Sitter based
major modes, LSP support via Eglot, etc. Thus, volunteers are welcome
to contribute additional features that will make Emacs a better IDE,
and ease the learning curve for newcomers.
Thank you for your interest in Emacs.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-11-23 6:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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-23 6:59 ` Eli Zaretskii
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).