all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: "Emacs Lisp Packages" chapter in the Emacs manual
Date: Sat, 16 May 2020 21:39:54 +0900	[thread overview]
Message-ID: <77039A1F-FAA2-41FE-86D4-C162847CE02D@traduction-libre.org> (raw)
In-Reply-To: <831rnkdvqk.fsf@gnu.org>



> On May 16, 2020, at 19:23, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
>> Date: Wed, 13 May 2020 12:02:15 +0900
>> Cc: Drew Adams <drew.adams@oracle.com>, Emacs developers <emacs-devel@gnu.org>
>>> On May 13, 2020, at 11:46, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>>> 
>>>>> +The traditional way to install Emacs Lisp code is to either install it
>>> [...]
>>>> "If an Emacs Lisp file is installed in the Emacs Lisp load path (defined
>>> 
>>> Nitpick: one says "file" the other "code".
>>> I think "file" is right.
>> 
>> Thank you.
> 
> Thanks, I installed a more detailed description of these matters along
> the lines you suggested.

I just checked out master and I'm not seeing it. Did you install it somewhere else ?


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





  reply	other threads:[~2020-05-16 12:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 15:02 "Emacs Lisp Packages" chapter in the Emacs manual Jean-Christophe Helary
2020-05-09 15:19 ` Stefan Kangas
2020-05-09 16:47   ` Jean-Christophe Helary
2020-05-10  2:19     ` Jean-Christophe Helary
2020-05-10 14:17       ` Stefan Monnier
2020-05-10 15:05         ` Jean-Christophe Helary
2020-05-10 16:49           ` Stefan Monnier
2020-05-10 17:13             ` Jean-Christophe Helary
2020-05-10 19:28               ` Drew Adams
2020-05-11  1:02                 ` Jean-Christophe Helary
2020-05-10 19:35               ` Stefan Monnier
2020-05-11  1:08                 ` Jean-Christophe Helary
2020-05-11  1:51                   ` Drew Adams
2020-05-11  3:26                     ` Stefan Monnier
2020-05-11  4:23                       ` Drew Adams
2020-05-11  4:40                         ` Stefan Monnier
2020-05-11  6:57                           ` Jean-Christophe Helary
2020-05-11 15:09                             ` Stefan Monnier
2020-05-11 15:23                               ` Drew Adams
2020-05-12  0:59                               ` Jean-Christophe Helary
2020-05-12  3:21                                 ` Stefan Monnier
2020-05-12  3:50                                   ` Jean-Christophe Helary
2020-05-12 15:46                                     ` Drew Adams
2020-05-13  1:43                                       ` Jean-Christophe Helary
2020-05-13  2:05                                         ` Drew Adams
2020-05-13  2:27                                           ` Jean-Christophe Helary
2020-05-13  2:33                                             ` Drew Adams
2020-05-13  2:46                                         ` Stefan Monnier
2020-05-13  3:02                                           ` Jean-Christophe Helary
2020-05-16 10:23                                             ` Eli Zaretskii
2020-05-16 12:39                                               ` Jean-Christophe Helary [this message]
2020-05-16 14:38                                                 ` Eli Zaretskii
2020-05-16 15:20                                                   ` Jean-Christophe Helary
2020-05-12 15:46                                 ` Drew Adams
2020-05-11 15:13                             ` Drew Adams
2020-05-12  3:18                               ` Richard Stallman
2020-05-11  3:23                   ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=77039A1F-FAA2-41FE-86D4-C162847CE02D@traduction-libre.org \
    --to=jean.christophe.helary@traduction-libre.org \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.