From: Eli Zaretskii <eliz@gnu.org>
To: "Etienne Prud’homme" <e.e.f.prudhomme@gmail.com>
Cc: stephen_leake@stephe-leake.org, rms@gnu.org,
drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: docstrings and elisp reference
Date: Fri, 09 Jun 2017 10:08:34 +0300 [thread overview]
Message-ID: <83poed7i4t.fsf@gnu.org> (raw)
In-Reply-To: <877f0ln3dx.fsf@x230.lts> (message from Etienne Prud’homme on Fri, 09 Jun 2017 01:20:26 -0400)
> From: Etienne Prud’homme <e.e.f.prudhomme@gmail.com>
> Date: Fri, 09 Jun 2017 01:20:26 -0400
> Cc: stephen_leake@stephe-leake.org, drew.adams@oracle.com, emacs-devel@gnu.org
I think I've said enough in this thread, so just 2 more comments:
> That is where _most_ GNU projects seem to lack the capability. It looks
> like Jean-Christophe was right in pointing out it might be because we’re
> not using HTML exporting templates at its best.
>
> GNU projects are usually harder to index because of that. Thus we have
> a minority of GNU tools listed. I’m not saying that for criticizing
> GNU, but I think it’s an important issue we could address in the near
> future.
Texinfo can produce HTML (which can be customized) and XML from the
Texinfo sources. These facilities can be used to enhance the
"indexing" (I'd call it "tagging" instead, to discern from the indices
we have in the manuals) of the produced documentation, if that is the
feature you think is missing in the Info manuals. Then preparing a
document in the structure you want for any GNU project should be very
easy. It's possible that the Texinfo language might need some
additions to support some of that, but that should be no problem,
given the active development of the Texinfo package.
> Of course, this discussion is about Emacs.
And therein is my second issue: reading the Bash and the ELisp manuals
in Zeal, I'm presented with exactly the same contents as when I read
them in Emacs's Info. IOW, what I have in Zeal is an Info browser
without the index-searching facilities which make Info so efficient
for me. So for me, and especially in the context of Emacs, it makes
very little sense to talk about these browsers, because they seem to
give be a subset of what we already have in Info. Perhaps I'm missing
something important.
next prev parent reply other threads:[~2017-06-09 7:08 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 21:26 docstrings and elisp reference Jean-Christophe Helary
2017-06-06 0:09 ` Tino Calancha
2017-06-06 5:10 ` Jean-Christophe Helary
2017-06-06 15:03 ` Eli Zaretskii
2017-06-06 20:25 ` Stephen Leake
2017-06-06 20:36 ` Drew Adams
2017-06-08 2:29 ` Etienne Prud’homme
2017-06-08 3:48 ` Jean-Christophe Helary
2017-06-08 5:39 ` Chad Brown
2017-06-08 8:12 ` Jean-Christophe Helary
2017-06-08 15:11 ` Eli Zaretskii
2017-06-08 15:42 ` Jean-Christophe Helary
2017-06-09 0:25 ` Chad Brown
2017-06-08 18:29 ` Etienne Prud’homme
2017-06-09 4:10 ` Richard Stallman
2017-06-08 15:18 ` Eli Zaretskii
2017-06-08 18:10 ` Etienne Prud’homme
2017-06-08 19:14 ` Eli Zaretskii
2017-06-08 20:07 ` Drew Adams
2017-06-08 20:22 ` Etienne Prud’homme
2017-06-08 22:44 ` Jean-Christophe Helary
2017-06-09 4:10 ` Richard Stallman
2017-06-09 5:20 ` Etienne Prud’homme
2017-06-09 7:08 ` Eli Zaretskii [this message]
2017-06-09 8:27 ` Yuri Khan
2017-06-09 9:38 ` Eli Zaretskii
2017-06-09 12:21 ` Eli Zaretskii
2017-06-09 12:32 ` Yuri Khan
2017-06-09 13:46 ` Eli Zaretskii
2017-06-09 19:24 ` Etienne Prud’homme
2017-06-10 1:06 ` Jean-Christophe Helary
2017-06-10 11:36 ` Nikolay Kudryavtsev
2017-06-10 14:26 ` Drew Adams
2017-06-10 3:19 ` Richard Stallman
2017-06-10 7:31 ` Eli Zaretskii
2017-06-11 2:43 ` Richard Stallman
2017-06-11 2:44 ` Richard Stallman
2017-06-11 15:18 ` Stefan Monnier
2017-06-12 2:52 ` Richard Stallman
2017-06-12 3:27 ` Stefan Monnier
2017-06-13 3:25 ` Richard Stallman
2017-06-10 8:22 ` Yuri Khan
2017-06-10 3:19 ` Richard Stallman
2017-06-06 20:45 ` Joost Kremers
2017-06-07 13:03 ` Stefan Monnier
2017-06-07 13:23 ` Yuri Khan
2017-06-07 13:31 ` Stefan Monnier
2017-06-07 14:18 ` Drew Adams
2017-06-07 15:43 ` Eli Zaretskii
2017-06-06 20:47 ` Dmitry Gutov
2017-06-06 21:21 ` Drew Adams
2017-06-06 21:50 ` Dmitry Gutov
2017-06-07 5:28 ` Eli Zaretskii
2017-06-17 12:46 ` Dmitry Gutov
2017-06-17 13:04 ` Alan Mackenzie
2017-06-17 13:55 ` Dmitry Gutov
2017-06-17 20:14 ` Alan Mackenzie
2017-06-18 2:32 ` Eli Zaretskii
2017-06-18 19:52 ` Richard Stallman
2017-06-17 22:13 ` Richard Stallman
2017-06-20 18:05 ` John Wiegley
2017-06-17 14:10 ` Eli Zaretskii
2017-06-17 15:13 ` Stefan Monnier
2017-06-17 18:59 ` Paul Eggert
2017-06-17 14:52 ` Drew Adams
2017-06-19 18:31 ` Thien-Thi Nguyen
2017-06-07 14:05 ` Drew Adams
2017-06-07 14:27 ` Drew Adams
2017-06-08 1:27 ` Richard Stallman
2017-06-06 22:42 ` Richard Stallman
2017-06-06 22:49 ` Dmitry Gutov
2017-06-07 5:20 ` Eli Zaretskii
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=83poed7i4t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=e.e.f.prudhomme@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=stephen_leake@stephe-leake.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).