From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Lawrence Bottorff <borgauf@gmail.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: [ANN] An impudent introduction to Guile
Date: Wed, 10 Feb 2016 20:47:58 +0100 [thread overview]
Message-ID: <CAMFYt2ag7=E9t07B1peQJtSO0_tEnfHTubdM5154Z1LiyQ_twQ@mail.gmail.com> (raw)
In-Reply-To: <CAFAhFSXqCHJm7=vgV7oRThw1E1rYt6xt4+oQdgqbeXgvHRkjnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
:)
2016-02-09 19:41 GMT+01:00 Lawrence Bottorff <borgauf@gmail.com>:
> Good, good.
>
>
>> 3. I'm not quite convinced whether \texttt{equivalence-classes} should
>> be replaced with \textit{equivalence-classes}. If we actually decide
>> to do so, I think it would be better to replace it as
>> \textit{equivalence classes}. However, although the italics are
>> actually used to refer to new notions, and typewriter font to refer to
>> notions/functions defined in Scheme, that use case is closer to
>> mentioning, than defining -- and I thought it would fall into memory
>> easier if the reader could see that "this is actually a Scheme
>> function indeed". (This won't be obvious during the first reading, so
>> I think it would be best to put the decision off for now)
>>
>
> good . . . it's just that it bleeds into the margin (on your original pdf)
> . . . any way to correct that?
>
Now I see. I think we would need some TeXpErT to have a look. Or perhaps it
would look nicer if a space was inserted before the dash, i.e.
\texttt{equivalence -classes}. Or maybe it's not worth the trouble and your
soltion with \textit is satisfactory.
5. I think you got the "reading programs isn't like reading novels"
>> (196) opposite to my intention, which was that the programs have a
>> higher level of generality (which is rather unfamiliar) -- novels are
>> more concrete and less general.
>>
>
> Changed it to ". . . Because of their familiar narrative specificity, we
> typically absorb stories almost effortlessly."
>
This seems fine :)
Thank you
[-- Attachment #2: Type: text/html, Size: 2792 bytes --]
next prev parent reply other threads:[~2016-02-10 19:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 0:47 [ANN] An impudent introduction to Guile Cao Jin
2016-02-06 6:08 ` Panicz Maciej Godek
2016-02-06 8:52 ` Arne Babenhauserheide
2016-02-06 9:16 ` Cao Jin
2016-02-06 10:18 ` Jan Wedekind
2016-02-07 9:54 ` A0
2016-02-07 21:51 ` Lawrence Bottorff
2016-02-08 19:58 ` Panicz Maciej Godek
2016-02-08 20:31 ` An impudent introduction to impudence Keith Wright
2016-02-09 6:29 ` Panicz Maciej Godek
2016-02-09 8:26 ` [ANN] An impudent introduction to Guile tomas
2016-02-09 18:41 ` Lawrence Bottorff
2016-02-10 19:47 ` Panicz Maciej Godek [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-04 23:09 Panicz Maciej Godek
2016-02-05 0:30 ` Christopher Allan Webber
[not found] ` <CAMFYt2YkMi2X0G_7eTtwkc66w1UhXndy+z91ui+PF6d0ie2Rug@mail.gmail.com>
[not found] ` <87zivfxg1w.fsf@dustycloud.org>
2016-02-05 21:46 ` Panicz Maciej Godek
2016-02-05 6:48 ` Shakthi Kannan
2016-02-05 18:55 ` Amirouche Boubekki
2016-02-05 22:09 ` Panicz Maciej Godek
2016-02-05 19:46 ` Lawrence Bottorff
2016-02-05 20:29 ` Panicz Maciej Godek
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='CAMFYt2ag7=E9t07B1peQJtSO0_tEnfHTubdM5154Z1LiyQ_twQ@mail.gmail.com' \
--to=godek.maciek@gmail.com \
--cc=borgauf@gmail.com \
--cc=guile-user@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.
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).