From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Imports / inclusion of s.el into Emacs Date: Sun, 03 May 2020 19:51:36 +0300 Message-ID: <83ees1otbb.fsf@gnu.org> References: <831ro2tqqx.fsf@gnu.org> <4a1fd3f4-df92-c756-9874-4d07b54148ac@yandex.ru> <83v9lesapw.fsf@gnu.org> <83pnbms9m8.fsf@gnu.org> <83a72qs4z2.fsf@gnu.org> <83wo5uqoh5.fsf@gnu.org> <838si9qf7s.fsf@gnu.org> <83pnblov3t.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="65436"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, emacs-devel@gnu.org, joaotavora@gmail.com, dgutov@yandex.ru, monnier@iro.umontreal.ca To: Yuri Khan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 03 18:52:27 2020 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 1jVHqt-000Gwa-Kh for ged-emacs-devel@m.gmane-mx.org; Sun, 03 May 2020 18:52:27 +0200 Original-Received: from localhost ([::1]:56400 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jVHqs-0006cA-M4 for ged-emacs-devel@m.gmane-mx.org; Sun, 03 May 2020 12:52:26 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42716) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVHqR-000698-7q for emacs-devel@gnu.org; Sun, 03 May 2020 12:51:59 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56052) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jVHqQ-00042l-1r; Sun, 03 May 2020 12:51:58 -0400 Original-Received: from [176.228.60.248] (port=1733 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jVHqA-0001zg-Vh; Sun, 03 May 2020 12:51:45 -0400 In-Reply-To: (message from Yuri Khan on Sun, 3 May 2020 23:32:01 +0700) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:248720 Archived-At: > From: Yuri Khan > Date: Sun, 3 May 2020 23:32:01 +0700 > Cc: Philippe Vaucher , Dmitry Gutov , > Richard Stallman , João Távora , > Stefan Monnier , Emacs developers > > On Sun, 3 May 2020 at 23:13, Eli Zaretskii wrote: > > > Tutorials are generally read only once, > > when you first familiarize yourself with a topic and generally want > > just the "taste" of it. Once you are past that step, there's no > > reason to go back to the tutorial, and the reference manual is the > > main tool for learning and doing. > > > > And yet you insist on seeing "tutorial-style" lists each time you need > > some API, but don't really know which. Why? this doesn't sound like > > what people use tutorials for. > > API lists are not tutorials. Are you saying this to me or to Philippe? It was him who brought up the tutorial analogy. I just responded to that. > They are the reference manual, just presented in a very condensed > form. A user who is moderately experienced with an API but has not > committed it into memory will sometimes forget exact names of > functions, and a concise API list will refresh his/her memory just > enough to continue coding. We've been there, let's not make another round of the same arguments.