unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: list of elisp primitives ?
Date: Fri, 27 Dec 2019 03:22:07 +0900	[thread overview]
Message-ID: <FE0557F6-5F23-4723-95A4-D70399470139@traduction-libre.org> (raw)
In-Reply-To: <153c262b-d4f6-4fc4-9fc2-57c58312ae1f@default>



> On Dec 27, 2019, at 3:09, Drew Adams <drew.adams@oracle.com> wrote:
> 
> Don't confuse building blocks for implementing Lisp
> in C with building blocks for defining Lisp in Lisp,
> which I suspect is really what you're after: a set
> of primitive Lisp constructs that can be used to
> define the rest of the language.

Well, I really don't want to redefine the language.

I just want to do simple file i/o and error handling etc. without having to worry about "and you can also do this and that by using that function and by setting this variable you can also do that" which is what the elisp reference is full of.

In my attempt at inserting an xml block into a RSS feed, I was presented with a number of different ways to do that, none corresponding to the functions I'd have picked by reading the reference. Same for error handling (and without help from the list I'd be stuck between sentences trying to make sense of the reference).

I'm fine with "there is more than one way to do it", but sometimes the subtle differences don't make much sense.

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune





  reply	other threads:[~2019-12-26 18:22 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 [this message]
2019-12-26 18:33             ` Stefan Monnier
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=FE0557F6-5F23-4723-95A4-D70399470139@traduction-libre.org \
    --to=jean.christophe.helary@traduction-libre.org \
    --cc=emacs-devel@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).