From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: list of elisp primitives ? Date: Thu, 26 Dec 2019 13:33:14 -0500 Message-ID: References: <627F3815-987E-4E82-8118-EE559CA7721F@traduction-libre.org> <5E53A27C-7C86-4275-AC12-9799C3CB1956@traduction-libre.org> <701C773A-96C5-47FD-B75F-92947976E57B@traduction-libre.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="113995"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Emacs developers To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 26 19:34:06 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ikXxW-000TYq-JB for ged-emacs-devel@m.gmane.org; Thu, 26 Dec 2019 19:34:06 +0100 Original-Received: from localhost ([::1]:55886 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ikXxV-0003Uh-Fc for ged-emacs-devel@m.gmane.org; Thu, 26 Dec 2019 13:34:05 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42922) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ikXwn-0002o2-2B for emacs-devel@gnu.org; Thu, 26 Dec 2019 13:33:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ikXwl-00063s-OV for emacs-devel@gnu.org; Thu, 26 Dec 2019 13:33:20 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:59333) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ikXwl-000639-IF for emacs-devel@gnu.org; Thu, 26 Dec 2019 13:33:19 -0500 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 4455510058D; Thu, 26 Dec 2019 13:33:18 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id CC15C100311; Thu, 26 Dec 2019 13:33:16 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1577385196; bh=mu7i+UtEKLEB+U4yeIUY1/g+EoE9JqqywFIPpfv3h/0=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=fYwnds/TrJypxbuVqRrqeHxKCapXdP9JCGupcJUm1a2jW/b8X01ZdlJg3oTqJPHq7 Q0lenpAKHBgibMhlutWHtD80GORZ5dG6+43AIWgC9wyL7hC3TqUkiecDakwh+NYb4A FLIjU1P9uVeRQhjDQ0g9a2EcQFoMjTFUH1czQyzoEsCqwcusvgamRvB1FMq0I83nCz bsrcF3AYAiuL7J66SREWqx87iXNO6JvGZfF9D42JCgOn6wRCdaPCZ1m6MbxLjWx2cH 7C77HvDnbG13lG9ByFCTmcc4XHlJkdbM9NKJYYlFs2822QNe0Hwd5zfeBqIXqUS/k4 K9End6akFWcfw== Original-Received: from alfajor (69-165-143-56.dsl.teksavvy.com [69.165.143.56]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 92BEC12131A; Thu, 26 Dec 2019 13:33:16 -0500 (EST) In-Reply-To: <701C773A-96C5-47FD-B75F-92947976E57B@traduction-libre.org> (Jean-Christophe Helary's message of "Fri, 27 Dec 2019 02:39:09 +0900") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 132.204.25.50 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243672 Archived-At: > Hence, knowing the building blocks (or a few dozen useful ones) can give > a clearer idea of what to do with elisp in general. I fully agree in theory. But it's quite difficult to know what those few blocks should be in general. To some extent the Elisp Intro provides this for the "general Elisp" context, but as soon as you get to writing real Elisp code, it's not "general" any more and you get into details specific to various packages and features (syntax-table, buffers, files, font-lock, indentation, ...). I think the best solution is to find humans to help you find the answers your questions. We also provide reference material for those cases where human help is not available or not sufficient, but it's hard to make such info work the way you describe for "all" the possible interests of the reader. Stefan