unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dieter@duenenhof-wilhelm.de (H. Dieter Wilhelm)
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: inform
Date: Fri, 08 May 2020 13:06:17 +0200	[thread overview]
Message-ID: <86r1vuit3q.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <83v9l6iv0g.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 May 2020 13:25:03 +0300")

>>    when (string= (file-name-nondirectory Info-current-file) "emacs").
>
> I think there are several more manuals to be added to the list.
> Basically, any manual that describes some Emacs facility should be
> there.  Examples include elisp, eintr, ebrowse, eieio, cl, tramp, and
> many others.

Absolutely.

I'll collect the "standard" documentation which will be more or less
eternal.  Thank you for the first pointer.  

And my hope is that a package repository maintainer is coming up with a
way to update programatically the growing?, ephemeral? Elpa, Melpa
texinfo documentation.

       Dieter

PS: Wasn't it decided on this list to change the name "eintr" for the
Elisp Introduction?

-- 
Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany



  reply	other threads:[~2020-05-08 11:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 19:36 [ELPA] New package: inform H. Dieter Wilhelm
2020-05-07 20:40 ` Stefan Monnier
2020-05-08  1:34   ` T.V Raman
2020-05-08  8:29     ` H. Dieter Wilhelm
2020-05-08  8:18   ` H. Dieter Wilhelm
2020-05-08 10:25     ` Eli Zaretskii
2020-05-08 11:06       ` H. Dieter Wilhelm [this message]
2020-05-08 11:39         ` Eli Zaretskii
2020-05-08 13:45         ` H. Dieter Wilhelm
2020-05-08 14:01           ` Eli Zaretskii
2020-05-08 15:04           ` Stefan Monnier
2020-05-10 18:19             ` H. Dieter Wilhelm
2022-12-25  9:39               ` Ihor Radchenko
2022-12-26  0:10                 ` Stefan Monnier
2022-12-26 20:41                   ` H. Dieter Wilhelm
2022-12-27 10:54                     ` Ihor Radchenko
2022-12-27 22:38                       ` H. Dieter Wilhelm
2020-05-08 11:45       ` Maurizio Boriani
2020-05-08 16:23     ` Drew Adams
2020-05-08 16:38       ` Drew Adams
2020-05-08 18:53       ` H. Dieter Wilhelm
2020-05-08 21:55         ` Drew Adams
2020-05-08 22:02           ` Drew Adams
2020-05-09  9:46       ` Jean-Christophe Helary
2020-05-09 13:06         ` help-fns+ (WAS: [ELPA] New package: inform) Noam Postavsky
2020-05-09 13:16           ` Jean-Christophe Helary
2020-05-09 17:27         ` [ELPA] New package: inform Drew Adams
2020-05-10  1:05           ` Jean-Christophe Helary
2020-05-09 17:10   ` H. Dieter Wilhelm
2023-02-01 19:08   ` H. Dieter Wilhelm
2023-02-01 19:21     ` H. Dieter Wilhelm
2020-05-09  3:51 ` Richard Stallman
2020-05-09  9:38   ` H. Dieter Wilhelm
2020-05-09  9:51     ` Eli Zaretskii
2020-05-09 15:29       ` H. Dieter Wilhelm

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=86r1vuit3q.fsf@duenenhof-wilhelm.de \
    --to=dieter@duenenhof-wilhelm.de \
    --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 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).