From: Mario Lang <mlang@delysid.org>
To: emacs-devel@gnu.org
Subject: Re: Info Pages for ELPA packages
Date: Tue, 27 May 2014 12:06:59 +0200 [thread overview]
Message-ID: <87y4xn358c.fsf@fx.delysid.org> (raw)
In-Reply-To: <jwvsinwv3ek.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 26 May 2014 13:54:39 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> So improving the GNU ELPA scripts to generate the Info and "dir" files
> would probably be a good first step. If you have specific packages
> which included docs in the Git repo but no Info&dir files, please send
> them along, they'll be helpful to try and figure out how those scripts
> could/should work.
packages/debbugs comes to mind, which has debbugs.texi but no .info.
packages/enwc also has a texi file but no info/dir, but the texi looks
rather short/incomplete.
packages/dismal also has a dismal-manual.texi (the name probably needs
changing) but no .info/dir files.
--
CYa,
⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/>
.''`. | Get my public key via finger mlang/key@db.debian.org
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`- <URL:http://delysid.org/> <URL:http://www.staff.tugraz.at/mlang/>
next prev parent reply other threads:[~2014-05-27 10:06 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
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 [this message]
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=87y4xn358c.fsf@fx.delysid.org \
--to=mlang@delysid.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).