unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Hartwig <mandyke@gmail.com>
To: guile-devel@gnu.org
Subject: Re: About REPL hook
Date: Sun, 2 Dec 2012 10:59:45 +0800	[thread overview]
Message-ID: <CAN3veRfOMWUhYa5fQ=oVatn6rw7QVjH-WZ=gFDzd59-ZqA+h6g@mail.gmail.com> (raw)
In-Reply-To: <1354379482.11146.147.camel@Renee-desktop.suse>

On 2 December 2012 00:31, nalaginrut <nalaginrut@gmail.com> wrote:
> I think a colorized REPL is useful for our users.
> Will you accept a patch to 'pp' for colorized REPL? Or an easy way, a
> module with hook to do the same job, but output twice?

Perhaps rather implement this as a separate, “advanced” interface.
Think: ipython vs. python.  Most of the existing repl module would be
reusable for such a task.

There are benefits to keeping the official package, shell, repl,
interface, whatsit free of unnecessary features.  Such simplicity aids
in debugging, and facilitates a clear definition of language
semantics, compatibility, portability, extension, etc..

Also, are you aware of the multiple existing packages that provide
provide a Guile REPL with syntax highlighting (and *much* more)?.  Try
Geiser [1] or Quack [2], both of which run inside emacs and provide
integration between file and repl buffers (i.e. run expressions
directly from file buffers).

Regards

[1] http://www.nongnu.org/geiser/
[2] http://www.neilvandyke.org/quack/



  reply	other threads:[~2012-12-02  2:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28  9:53 About REPL hook nalaginrut
2012-11-30 10:49 ` Ludovic Courtès
2012-12-01 16:31   ` nalaginrut
2012-12-02  2:59     ` Daniel Hartwig [this message]
2012-12-02 15:39       ` nalaginrut
2012-12-02 16:50     ` Ludovic Courtès
2012-12-03  2:18       ` nalaginrut

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='CAN3veRfOMWUhYa5fQ=oVatn6rw7QVjH-WZ=gFDzd59-ZqA+h6g@mail.gmail.com' \
    --to=mandyke@gmail.com \
    --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).