From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs website, Lisp, and other Date: Wed, 07 Aug 2024 14:13:52 +0300 Message-ID: <86h6bwoaa7.fsf@gnu.org> References: <87sevj9b50.fsf@jeremybryant.net> <86h6bzqj2v.fsf@gnu.org> <87ed718o45.fsf@jeremybryant.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40376"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, rms@gnu.org To: Jeremy Bryant Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 07 13:14:58 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sbed7-000AOC-QK for ged-emacs-devel@m.gmane-mx.org; Wed, 07 Aug 2024 13:14:57 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sbecW-0002ut-LL; Wed, 07 Aug 2024 07:14:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sbecQ-0002ui-Pf for emacs-devel@gnu.org; Wed, 07 Aug 2024 07:14:15 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sbecP-0007w5-5s; Wed, 07 Aug 2024 07:14:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=iNrA2/mlstWjSduSDEvzopW85mtkIElQw8pXX7H5Oqc=; b=q+TrVAZbnlW8 W7rvsVGqaY5ztZDCZBuCWzRKVnYCT740s3OD1nW3uDLoe/bFUETnR+h0BLiJOTMJdzeLiLDD93wDA ADBbYZtI/nHiwwtNcCxmaWOfcpU6tjA/Z901jyXs4I3SVIJ2QvZMoDcn9XgUyIwhtDjVCSmgRw+DO iu7mUkUNMsFuSn1woekUknVWi2EV1NxS3xOVGlSyiA6fIbzYAlCMx8BrVN0ltFaHKgjRqXOugy1v5 /03veQS6uHyJdHiMZFT682tUiFYdsXD8kHkPD7cY0c0Yj+buwOnT/pcDNyc60iO2H9B+VgjALumM5 iKVhTUCz/5UAp5BRqII/GA==; In-Reply-To: <87ed718o45.fsf@jeremybryant.net> (message from Jeremy Bryant on Tue, 06 Aug 2024 20:09:30 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:322493 Archived-At: > From: Jeremy Bryant > Cc: emacs-devel@gnu.org, rms@gnu.org > Date: Tue, 06 Aug 2024 20:09:30 +0100 > > Eli Zaretskii writes: > > >> From: Jeremy Bryant > >> 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.