unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mario Lang <mlang@delysid.org>
To: "T. V. Raman" <raman@google.com>
Cc: tv.raman.tv@gmail.com, emacs-devel@gnu.org
Subject: Re: Info Pages for ELPA  packages
Date: Mon, 26 May 2014 00:05:57 +0200	[thread overview]
Message-ID: <8761ktpl8a.fsf@fx.delysid.org> (raw)
In-Reply-To: <21377.12999.817056.616859@gargle.gargle.HOWL> (T. V. Raman's message of "Sat, 24 May 2014 17:01:11 -0700")

"T. V. Raman" <raman@google.com> writes:

> I've noticed myself installing elpa packages, then pulling their
> sources   from some git repo purely to get at the package's info
> files or other documentation. Can we have  some  affordance in
> elpa that allows packages to have info docs or documentation of
> some sort alongside elpa? 

We have that already.  Just place a package-name.info and a "dir" file
in the same directory as package-name.el.  It will automatically be
picked up on package installation.  Documented in a paragraph of the
"Multi-file package" section in the elisp info manual.

-- 
CYa,
  ⡍⠁⠗⠊⠕



  parent reply	other threads:[~2014-05-25 22:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-25  0:01 Info Pages for ELPA packages T. V. Raman
2014-05-25  1:41 ` Glenn Morris
2014-05-25 22:05 ` Mario Lang [this message]
2014-05-26  4:37   ` raman
2014-05-26 17:54     ` Stefan Monnier
2014-05-26 22:38       ` T.V Raman
2014-05-27  2:40       ` Eric Abrahamsen
2014-05-27  2:47         ` raman
2014-05-27  3:25           ` Stefan Monnier
2014-05-27 15:23             ` T.V Raman
2014-05-27 16:03               ` Stephen J. Turnbull
2014-05-27 19:49               ` Stefan Monnier
2014-05-27  3:26         ` Stefan Monnier
2014-05-27  4:43           ` Eric Abrahamsen
2014-05-27 10:06       ` Mario Lang
2014-05-27 11:50         ` Michael Albinus

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=8761ktpl8a.fsf@fx.delysid.org \
    --to=mlang@delysid.org \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.com \
    --cc=tv.raman.tv@gmail.com \
    /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).