From: Nala Ginrut <nalaginrut@gmail.com>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: bug#13077: guile: add repl-option for customized print
Date: Wed, 12 Dec 2012 13:49:30 +0800 [thread overview]
Message-ID: <1355291370.2835.18.camel@Renee-desktop.suse> (raw)
In-Reply-To: <CAN3veReFezFeGSLmj=RDgm1ke-HONvyBwdqHkibgzDrw8kswww@mail.gmail.com>
On Wed, 2012-12-12 at 13:00 +0800, Daniel Hartwig wrote:
> [No need to Cc the bug report]
>
> On 12 December 2012 12:03, Nala Ginrut <nalaginrut@gmail.com> wrote:
> > Seems (fluid-ref *repl-stack*) is not a pair/list when REPL is just
> > started?
>
> Correction: is not a pair/list when /guile/ is just started. The
> program, guile, is not a REPL, that is only an optional component of
> it.
>
> You can't set REPL options before there is a REPL. The rc file
> (.guile) is applicable to all of guile, and read during initialization
> which is before any REPL is created.
>
> Try repl-default-option-set!.
repl-default-option-set! seems didn't make sense. How can I check the
REPL exist? My idea is to do that after I detected the REPL existed.
I believe people more like to activate the colored-REPL automatically
when ~/.guile is setup. Rather than call (activate-colorized) manually,
just like 'readline' module does.
Regards.
next prev parent reply other threads:[~2012-12-12 5:49 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 [this message]
[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
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=1355291370.2835.18.camel@Renee-desktop.suse \
--to=nalaginrut@gmail.com \
--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).