unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: list of elisp primitives ?
Date: Thu, 26 Dec 2019 13:33:14 -0500	[thread overview]
Message-ID: <jwvsgl7c56n.fsf-monnier+emacs@gnu.org> (raw)
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")

> 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




  parent reply	other threads:[~2019-12-26 18:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-22  2:59 list of elisp primitives ? Jean-Christophe Helary
2019-12-22  3:21 ` Eduardo Ochs
2019-12-22  3:43   ` Jean-Christophe Helary
     [not found]     ` <CADs++6hB7ZKnEWOZ=XOGdA=W_CacCE2=354ARfNFtWvStaCF3g@mail.gmail.com>
2019-12-22  4:14       ` Jean-Christophe Helary
     [not found]         ` <CADs++6j+niJy3hvrTEJ-LrqcitFuffX=1Duca7pU30a8qfh_zg@mail.gmail.com>
2019-12-22  4:38           ` Jean-Christophe Helary
2019-12-22 15:01         ` Stephen Berman
2019-12-22 17:31         ` Drew Adams
2019-12-26 17:39           ` Jean-Christophe Helary
2019-12-26 18:00             ` arthur miller
2019-12-26 18:09             ` Drew Adams
2019-12-26 18:22               ` Jean-Christophe Helary
2019-12-26 18:33             ` Stefan Monnier [this message]
2019-12-26 21:17             ` Eduardo Ochs
2019-12-27  0:21               ` Jean-Christophe Helary
2019-12-22 14:56     ` Óscar Fuentes
2019-12-22 22:34       ` Jean-Christophe Helary
2019-12-22 19:21 ` Marcin Borkowski

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=jwvsgl7c56n.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@traduction-libre.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).