unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Jean Abou Samra <jean@abou-samra.fr>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: guile-devel@gnu.org
Subject: Re: Doc patches outstanding
Date: Tue, 17 Jan 2023 13:37:59 +0100	[thread overview]
Message-ID: <9c88efdb-858c-18b1-fb85-f4773c7174a8@abou-samra.fr> (raw)
In-Reply-To: <87r0vtoevp.fsf@web.de>


[-- Attachment #1.1: Type: text/plain, Size: 913 bytes --]



Le 17/01/2023 à 07:21, Dr. Arne Babenhauserheide a écrit :
> Hello Jean,
>
> Jean Abou Samra <jean@abou-samra.fr> writes:
>> Thank you for applying the first one nevertheless. I am attaching
>> patch files for the other two, that should work better.
> They are applied and pushed now — thank you, and thank you for your patience!
>
> For the eval-when-example I wrote a small change to the wording, because
> I found that the example actually runs in Guile 3.0.8, but retrieves the
> runtime value of the date-time instead of the compile-time value.
>
> Can you have a look? If it’s good to go from your side, I’d push it.


Well... you're right. Although it cannot be byte-compiled, it can be 
evaluated (actually, I find it surprising that evaluating a file 
evaluates the S-exprs one by one rather than first macroexpanding 
everything...).

You can push it.

Best,
Jean


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2023-01-17 12:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 18:52 Doc patches outstanding Jean Abou Samra
2022-12-11  2:05 ` Dr. Arne Babenhauserheide
2022-12-11 11:30   ` Jean Abou Samra
2023-01-10 15:51     ` Jean Abou Samra
2023-01-10 17:50       ` Dr. Arne Babenhauserheide
2023-01-17  6:21     ` Dr. Arne Babenhauserheide
2023-01-17 12:37       ` Jean Abou Samra [this message]
2023-01-17 19:02         ` Dr. Arne Babenhauserheide

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=9c88efdb-858c-18b1-fb85-f4773c7174a8@abou-samra.fr \
    --to=jean@abou-samra.fr \
    --cc=arne_bab@web.de \
    --cc=guile-devel@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).