From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mark Harig Newsgroups: gmane.lisp.guile.devel Subject: Re: Indexing Scheme and C identifiers separately Date: Sun, 24 Apr 2011 18:43:54 -0400 Message-ID: <8CDD0E83970C890-1820-11709@webmail-m029.sysops.aol.com> References: <8CDD0063C9BEB29-FC8-5987@web-mmc-d08.sysops.aol.com><8CDD0D662A18273-1820-10289@webmail-m029.sysops.aol.com> <20110424190907.7da62045@rascar> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--------MB_8CDD0E839817245_1820_1E2E2_webmail-m029.sysops.aol.com" X-Trace: dough.gmane.org 1303685070 19515 80.91.229.12 (24 Apr 2011 22:44:30 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 24 Apr 2011 22:44:30 +0000 (UTC) Cc: guile-devel@gnu.org To: david@altosw.be, wingo@pobox.com Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Mon Apr 25 00:44:26 2011 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QE82U-0005ZZ-2f for guile-devel@m.gmane.org; Mon, 25 Apr 2011 00:44:26 +0200 Original-Received: from localhost ([::1]:60361 helo=lists2.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QE82T-0005nL-JN for guile-devel@m.gmane.org; Sun, 24 Apr 2011 18:44:25 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:41820) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QE82Q-0005mz-05 for guile-devel@gnu.org; Sun, 24 Apr 2011 18:44:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QE82O-0006v8-S1 for guile-devel@gnu.org; Sun, 24 Apr 2011 18:44:21 -0400 Original-Received: from imr-ma03.mx.aol.com ([64.12.206.41]:43988) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QE82O-0006v4-MC for guile-devel@gnu.org; Sun, 24 Apr 2011 18:44:20 -0400 Original-Received: from imo-ma02.mx.aol.com (imo-ma02.mx.aol.com [64.12.78.137]) by imr-ma03.mx.aol.com (8.14.1/8.14.1) with ESMTP id p3OMi0k0004105; Sun, 24 Apr 2011 18:44:00 -0400 Original-Received: from idirectscm@aim.com by imo-ma02.mx.aol.com (mail_out_v42.9.) id w.103d.5bbb7d2 (45324); Sun, 24 Apr 2011 18:43:55 -0400 (EDT) Original-Received: from smtprly-mc01.mx.aol.com (smtprly-mc01.mx.aol.com [64.12.95.97]) by cia-mc04.mx.aol.com (v129.10) with ESMTP id MAILCIAMC048-d3c94db4a7aa14f; Sun, 24 Apr 2011 18:43:55 -0400 Original-Received: from webmail-m029 (webmail-m029.sim.aol.com [64.12.101.212]) by smtprly-mc01.mx.aol.com (v129.10) with ESMTP id MAILSMTPRLYMC013-d3c94db4a7aa14f; Sun, 24 Apr 2011 18:43:54 -0400 X-AOL-IP: 98.185.24.91 In-Reply-To: <20110424190907.7da62045@rascar> X-MB-Message-Source: WebUI Original-Received: from 98.185.24.91 by webmail-m029.sysops.aol.com (64.12.101.212) with HTTP (WebMailUI); Sun, 24 Apr 2011 18:43:54 -0400 X-MB-Message-Type: User X-Mailer: AIM WebMail 33636-STANDARD X-AOL-SENDER: idirectscm@aim.com X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 64.12.206.41 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:12334 Archived-At: ----------MB_8CDD0E839817245_1820_1E2E2_webmail-m029.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" 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 ...] >=20 > 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. >=20 > Cheers, > David >=20 > >> 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. =20 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. -- =20 ----------MB_8CDD0E839817245_1820_1E2E2_webmail-m029.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" 
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 ...]
>=20
> 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.
>=20
> Cheers,
> David
>=20

> >> 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. =20

   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.

--
 ----------MB_8CDD0E839817245_1820_1E2E2_webmail-m029.sysops.aol.com--