unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Andy Wingo <wingo@pobox.com>
Cc: Mark Harig <idirectscm@aim.com>, guile-devel@gnu.org
Subject: Re: Patch: New section "Invoking Guile" for chapter "Programming in Scheme"
Date: Sun, 24 Apr 2011 19:09:07 -0300	[thread overview]
Message-ID: <20110424190907.7da62045@rascar> (raw)
In-Reply-To: <m37hajbc0v.fsf@unquote.localdomain>

Le Sun, 24 Apr 2011 23:00:16 +0200,
Andy Wingo <wingo@pobox.com> a écrit :

> Hi Mark,
> 
> Thanks for the revisions.
> ..

Hello Mark,
Andy,

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

;;;
;;; here below, the 'most appropriate' email from the thread, I think
;;;

From: "Neil Jerram" <neiljerram@googlemail.com>
To: "David Séverin" <david@altosw.be>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Plan for 2.0
Date: Mon, 5 Jan 2009 13:47:00 +0000

2009/1/4 Neil Jerram <neiljerram@googlemail.com>:
> 2009/1/4 David Séverin <david@altosw.be>:  
>> 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.  
>
> Thanks for this idea!
>
> I'm not persuaded by the procedure/variable/type separation  

I'm sorry, that's complete nonsense, as we already have the
procedure/variable/type separation.

So in fact now I completely agree with what you've suggested.

Regards,
        Neil




  parent reply	other threads:[~2011-04-24 22:09 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 [this message]
2011-04-24 22:43         ` Indexing Scheme and C identifiers separately Mark Harig
2011-04-25  1:18           ` 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=20110424190907.7da62045@rascar \
    --to=david@altosw.be \
    --cc=guile-devel@gnu.org \
    --cc=idirectscm@aim.com \
    --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).