From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Glenn Morris <rgm@gnu.org>,
Aidan Gauland <aidalgol@no8wireless.co.nz>,
emacs-devel@gnu.org, Eric Ludlam <zappo@gnu.org>
Subject: Re: Missing texinfo manual
Date: Wed, 19 Jun 2013 21:10:52 -0400 [thread overview]
Message-ID: <51C2569C.1020400@siege-engine.com> (raw)
In-Reply-To: <87fvwopgx2.fsf@engster.org>
On 06/11/2013 03:48 PM, David Engster wrote:
> Glenn Morris writes:
>> Aidan Gauland wrote:
>>
>>> wisent.texi and bovine.texi contain references to the "grammar-fw"
>>> manual -- line 1580 in wisent.texi, and line 85 in bovine.texi -- but it
>>> is neither in trunk nor the (latest) Emacs release tarball.
>>
>> It's one of the (several?) CEDET manuals that has never been part of
>> Emacs. I can add it, if that is appropriate (David, Eric?).
>
> Not sure about that. I was never fond of the plethora of different info
> files in CEDET. I'd rather integrate grammar-fw in one of the other
> manuals, but I'm not sure where. Maybe in semantic.texi?
Hi,
A similar topic came up once before many years ago, and I had tried
merging some of the Semantic manuals together. If I remember, the
subsubsection levels got too deep, and my lack of texi skills led me
somewhere I wasn't sure how to fix.
The grammar-fw.texi file goes best with bovine.texi and wisent.texi -
the two grammar modes in Semantic, but merging those 3 doesn't seem
quite right to me. The semantic.texi manual refers to the other manuals
and has the 'internals' - a description the different files that make up
Semantic. Since semantic-fw is about the tools used to write grammars
more than the grammars themselves, I think that including it as a
chapter in semantic.texi would be fine, and is similar in scope to
'internals' which is also about where to find code in Semantic.
Unfortunately, I think the organic growth of those manuals has resulted
in a strange high-level organization. The simple change of @include-ing
grammar-fw.texi into semantic.texi will continue that trend. If anyone
has thoughts on a better way to address what David points out as a
"plethora of different info files", it can only make things better.
Thanks
Eric
next prev parent reply other threads:[~2013-06-20 1:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 21:01 Missing texinfo manual Aidan Gauland
2013-06-11 17:05 ` Glenn Morris
2013-06-11 19:48 ` David Engster
2013-06-11 20:29 ` Glenn Morris
2013-06-19 9:42 ` Aidan Gauland
2013-06-19 16:05 ` Glenn Morris
2013-06-19 19:35 ` David Engster
2013-06-20 1:10 ` Eric M. Ludlam [this message]
2013-06-24 2:21 ` Glenn Morris
2013-06-26 1:48 ` Glenn Morris
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=51C2569C.1020400@siege-engine.com \
--to=eric@siege-engine.com \
--cc=aidalgol@no8wireless.co.nz \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=zappo@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).