From: Mark Harig <idirectscm@aim.com>
To: david@altosw.be, wingo@pobox.com
Cc: guile-devel@gnu.org
Subject: Re: Indexing Scheme and C identifiers separately
Date: Sun, 24 Apr 2011 18:43:54 -0400 [thread overview]
Message-ID: <8CDD0E83970C890-1820-11709@webmail-m029.sysops.aol.com> (raw)
In-Reply-To: <20110424190907.7da62045@rascar>
[-- Attachment #1: Type: text/plain, Size: 2669 bytes --]
On Sun, Apr 24, 2011 at 07:09:07PM -0300, David Pirotte wrote:
> While you are at the manual, may I point to some
> suggestion I made about the structure and contents of the
> indexes which still is, IMHO, valid today. [wanted to
> actually really point the email in guile-devel archive but
> but it didn't let me parse before october 2009 ...]
>
> I didn't and still don't have [yet] the skill to fluently
> and bug freely manipulate large doc written in texinfo,
> otherwise I would have done it.
>
> Cheers,
> David
>
> >> Hi Guilers,
> >>
> >> It might be a small thing [and of course not a priority
> >> at all], but I'd love to see a small evolution of the
> >> manual index structure in order to separate scheme
> >> procedures from others, scheme variables from
> >> others...:
> >>
> >> * Concept Index
> >> * Scheme Prodedure Index * C Procedure Index
> >> * Scheme Variable Index * C Variable Index
> >> * Scheme Type Index * C Type Index
> >> * R5RS Index
> >>
> >> Being a scheme 'only' programmer, I'd love not to have
> >> to scroll through gh_* and scm_* ... when I am looking
> >> for something in an index.
I do not know how you are reading the Guile Reference
Manual, but the printed version is about 809 pages long. At
present, the indices run from page 755 to 809, so the
revision that is suggested, above, would not be small.
What would be of some help to get this project started is a
list of the identifiers:
1) A list of all Scheme procedure names
2) A list of all C procedure names
3) A list of all Scheme variable names
4) A list of all C variable names
5) A list of all Scheme type names
6) A list of all C type names
(By "all names", I mean "all names included in the Guile
Reference Manual", not, for example, "all C function names
in Standard C".)
To make the project more manageable, it could be done in
"atomic" sets.
1) Set 1 would be all Scheme and C procedure names
2) Set 2 would be all Scheme and C variable names
3) Set 3 would be all Scheme and C type names
Each of these sets could be added to the manual
independently over a period of time.
Also useful would be more suggestions for the Concept Index.
If you are using the reference manual and attempt to look
something up via the `Info-index' or `Info-virtual-index'
commands and are not able to locate what you are looking
for, then that is a good candidate for a report to the
bug-guile mailing list. A `@cindex' entry can then be added
to the appropriate locations in the manual, making it more
useful and easier to use.
--
[-- Attachment #2: Type: text/html, Size: 3302 bytes --]
next prev parent reply other threads:[~2011-04-24 22:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 19:46 Patch: New section "Invoking Guile" for chapter "Programming in Scheme" Mark Harig
2011-04-24 14:33 ` Andy Wingo
2011-04-24 20:36 ` Mark Harig
2011-04-24 21:00 ` Andy Wingo
2011-04-24 21:58 ` Mark Harig
2011-04-25 8:01 ` Andy Wingo
2011-04-24 22:09 ` David Pirotte
2011-04-24 22:43 ` Mark Harig [this message]
2011-04-25 1:18 ` Indexing Scheme and C identifiers separately Noah Lavine
2011-04-25 16:16 ` David Pirotte
2011-05-20 22:53 ` Neil Jerram
2011-04-25 19:49 ` Patch: New section "Invoking Guile" for chapter "Programming in Scheme" Mark Harig
2011-04-26 18:07 ` Neil Jerram
2011-04-26 21:01 ` Ludovic Courtès
2011-04-27 9:40 ` Andy Wingo
2011-04-27 10:23 ` Ludovic Courtès
2011-04-27 19:29 ` Neil Jerram
2011-04-27 16:54 ` Mark Harig
2011-04-27 19:40 ` Neil Jerram
2011-06-30 11:23 ` Andy Wingo
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8CDD0E83970C890-1820-11709@webmail-m029.sysops.aol.com \
--to=idirectscm@aim.com \
--cc=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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.
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).