unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jeremy Bryant <jb@jeremybryant.net>, emacs-devel@gnu.org, rms@gnu.org
Subject: Emacs website, Lisp, and other
Date: Wed, 7 Aug 2024 14:16:39 +0200	[thread overview]
Message-ID: <trinity-5348f26c-fb2e-466e-8515-515e5b30e6f5-1723032999546@3c-app-mailcom-bs15> (raw)
In-Reply-To: <86h6bwoaa7.fsf@gnu.org>

> Sent: Wednesday, August 07, 2024 at 11:13 PM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: "Jeremy Bryant" <jb@jeremybryant.net>
> Cc: emacs-devel@gnu.org, rms@gnu.org
> Subject: Re: Emacs website, Lisp, and other
>
> > From: Jeremy Bryant <jb@jeremybryant.net>
> > Cc: emacs-devel@gnu.org,  rms@gnu.org
> > Date: Tue, 06 Aug 2024 20:09:30 +0100
> > 
> > Eli Zaretskii <eliz@gnu.org> writes:
> > 
> > >> From: Jeremy Bryant <jb@jeremybryant.net>
> > >> Date: Sun, 04 Aug 2024 23:27:39 +0100
> > >> 
> > >> Reviewing the Emacs website, and previous discussions on this list below
> > >> (admittedly not recent, but still relevant).  It seems important to add
> > >> some text on Lisp which is not currently there, as per ideas of RMS and
> > >> Eli summarised below.
> > >
> > > Why is this important?
> > 
> > It appeared to be an outstanding documentation item to add to the
> > website, using the summary text written from RMS.
> > 
> > I personally believe it is important and useful in the context of an
> > introduction to Emacs such as the website.  For new users, or indeed
> > new contributors, Emacs Lisp may appear an intriguing choice, and that
> > summary offers a compelling reason for Lisp.
> 
> It is hard to find a good place there to talk about these aspects.
> The site introduces Emacs as an editor, and describes its important
> features.  Emacs being Emacs, that list is long, but far from
> comprehensive.  We could add a paragraph about Lisp there, but then
> (a) it would be most probably lost in the (quite long) introduction,
> and (b) there are many more aspects of Emacs of the same importance
> that could be added, and we must draw the line somewhere.
> 
> The way the site solves this dilemma is to focus on user-facing
> features.  The fact that Emacs is written in Lisp doesn't fit, IMO.
 
I agree.  Some detail could be added in the introduction to new users
(perhaps in an appendix if things do not fit together well enough).  

For new users, we should mention the immediate benefits.

Customization and Extensibility: Emacs allows users to tailor the editor 
to their specific needs, whether it’s through themes, keybindings, or 
custom commands.

Integration and Efficiency: Emacs integrates various workflows, from code 
editing to project management and even personal organization, offering a 
seamless and efficient experience.

We can also suggest learning paths for users who wish to explore Emacs Lisp 
further, ensuring that this advanced knowledge is available without being a 
barrier to entry.




  parent reply	other threads:[~2024-08-07 12:16 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-04 22:27 Emacs website, Lisp, and other Jeremy Bryant
2024-08-04 22:55 ` Emanuel Berg
2024-08-05  4:29   ` Emanuel Berg
2024-08-05  9:23   ` Christopher Dimech
2024-08-05 10:43     ` Emanuel Berg
2024-08-05 11:37       ` divya
2024-08-05 11:56         ` Christopher Dimech
2024-08-05 12:33         ` Eli Zaretskii
2024-08-05 11:45       ` Christopher Dimech
2024-08-05 12:56       ` Dr. Arne Babenhauserheide
2024-08-05 13:16         ` Dr. Arne Babenhauserheide
2024-08-05 14:46           ` Christopher Dimech
2024-08-05 21:28             ` Dr. Arne Babenhauserheide
2024-08-05 14:55         ` Eli Zaretskii
2024-08-05 12:28     ` Eli Zaretskii
2024-08-05 16:27       ` 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other) Emanuel Berg
2024-08-05 16:38         ` Eli Zaretskii
2024-08-05 17:03           ` Emanuel Berg
2024-08-05 18:32             ` 10 problems with Elisp, part 10 Dr. Arne Babenhauserheide
2024-08-05 20:20               ` Emanuel Berg
2024-08-06  7:14                 ` Dr. Arne Babenhauserheide
2024-08-06  7:21                   ` Org mode API (was: 10 problems with Elisp, part 10) Ihor Radchenko
2024-08-06  8:23                     ` Org mode API Dr. Arne Babenhauserheide
2024-08-10 16:55                       ` Ihor Radchenko
2024-08-06 11:54                   ` 10 problems with Elisp, part 10 Eli Zaretskii
2024-08-08  2:01                     ` Richard Stallman
2024-08-09 22:39                       ` Emanuel Berg
2024-08-13  1:28                         ` Richard Stallman
2024-08-09 22:46                     ` Emanuel Berg
2024-08-10  5:41                       ` Emanuel Berg
2024-08-10  6:09                         ` Eli Zaretskii
2024-08-13  1:28                       ` Richard Stallman
2024-08-05 18:58             ` 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other) Christopher Dimech
2024-08-05 19:30               ` 10 problems with Elisp, part 10 Dr. Arne Babenhauserheide
2024-08-05 20:02                 ` Christopher Dimech
2024-08-08  2:01                   ` Richard Stallman
2024-08-06  2:28                 ` Eli Zaretskii
2024-08-05 17:13         ` 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other) Yuri Khan
2024-08-06  6:39         ` Emanuel Berg
2024-08-06 11:16         ` Richard Stallman
2024-08-06 22:08           ` Emanuel Berg
2024-08-05 11:56 ` Emacs website, Lisp, and other Eli Zaretskii
2024-08-06 19:09   ` Jeremy Bryant
2024-08-06 19:50     ` Christopher Dimech
2024-08-06 20:35       ` [External] : " Drew Adams
2024-08-06 22:10         ` Dr. Arne Babenhauserheide
2024-08-06 22:48           ` Christopher Dimech
2024-08-06 23:09           ` Drew Adams
2024-08-06 23:21             ` Christopher Dimech
2024-08-07  1:09               ` Dr. Arne Babenhauserheide
2024-08-06 22:26         ` Christopher Dimech
2024-08-07  5:45         ` Emanuel Berg
2024-08-15  3:53           ` Madhu
2024-08-15  5:50             ` Emanuel Berg
2024-08-15  9:17               ` Madhu
2024-08-15  9:57                 ` Emanuel Berg
2024-08-15  6:17             ` Emanuel Berg
2024-08-15  7:10               ` Eli Zaretskii
2024-08-15  8:06               ` Emanuel Berg
2024-08-15  9:27                 ` Emanuel Berg
2024-08-15 16:03                   ` Emanuel Berg
2024-08-07 11:13     ` Eli Zaretskii
2024-08-07 12:03       ` Andrea Corallo
2024-08-07 12:16       ` Christopher Dimech [this message]
2024-08-08  2:01         ` Richard Stallman
2024-08-08  6:51           ` Joel Reicher
2024-08-07 12:31     ` Christopher Dimech
  -- strict thread matches above, loose matches on Subject: below --
2024-08-06 13:13 Abraham S.A.H. via Emacs development discussions.
2024-08-07  7:27 ` Emanuel Berg
2024-08-07 11:24   ` Christopher Dimech

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=trinity-5348f26c-fb2e-466e-8515-515e5b30e6f5-1723032999546@3c-app-mailcom-bs15 \
    --to=dimech@gmx.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=rms@gnu.org \
    /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).