From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: guile-devel@gnu.org, 13077@debbugs.gnu.org
Subject: Re: bug#13077: guile: add repl-option for customized print
Date: Tue, 04 Dec 2012 07:39:09 +0100 [thread overview]
Message-ID: <87lides4mq.fsf@zigzag.favinet> (raw)
In-Reply-To: <CAN3veReRKhsGip-jev8YyYf_xbTLFFK-bEN=9bR8BddatGWLKg__21131.9749746055$1354599399$gmane$org@mail.gmail.com> (Daniel Hartwig's message of "Tue, 4 Dec 2012 13:34:52 +0800")
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
() Daniel Hartwig <mandyke@gmail.com>
() Tue, 4 Dec 2012 13:34:52 +0800
patch that handles [...] *unspecified*
Can ‘unspecified?’ (the procedure) be used? I seem to recall people
wanting to avoid using ‘*unspecified*’ (the unique object) a while back.
--
Thien-Thi Nguyen ..................................... GPG key: 4C807502
. NB: ttn at glug dot org is not me .
. (and has not been since 2007 or so) .
. ACCEPT NO SUBSTITUTES .
........... please send technical questions to mailing lists ...........
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2012-12-04 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87hao21nte.fsf@gmail.com>
2012-12-04 5:19 ` bug#13077: guile: add repl-option for customized print nalaginrut
2012-12-04 5:34 ` Daniel Hartwig
2012-12-04 6:30 ` nalaginrut
2012-12-04 6:34 ` Daniel Hartwig
2012-12-12 4:03 ` Nala Ginrut
2012-12-12 5:00 ` Daniel Hartwig
2012-12-12 5:49 ` Nala Ginrut
[not found] ` <CAN3veRdDA-LwBhu7_Uthfj1h7HGzvFOPLoOtkoyd-MQOA+1Xug@mail.gmail.com>
2012-12-12 6:03 ` Daniel Hartwig
[not found] ` <CAN3veReRKhsGip-jev8YyYf_xbTLFFK-bEN=9bR8BddatGWLKg__21131.9749746055$1354599399$gmane$org@mail.gmail.com>
2012-12-04 6:39 ` Thien-Thi Nguyen [this message]
2012-12-04 7:36 ` Daniel Hartwig
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=87lides4mq.fsf@zigzag.favinet \
--to=ttn@gnuvola.org \
--cc=13077@debbugs.gnu.org \
--cc=guile-devel@gnu.org \
--cc=mandyke@gmail.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).