unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Adriano Peluso <randomlooser@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-user@gnu.org
Subject: Re: guile studio - question
Date: Sat, 19 Jun 2021 08:17:08 +0200	[thread overview]
Message-ID: <fb7fb2c6efd3c1449568f9f7eaca0e401e9a1724.camel@riseup.net> (raw)
In-Reply-To: <87sg1fo76p.fsf@elephly.net>

Il giorno ven, 18/06/2021 alle 11.25 +0200, Ricardo Wurmus ha scritto:


> Would you prefer a button in the toolbar that will always send the 
> code from the main buffer to the REPL?

Personally, I would prefer a toolbar with a button in it, yes

The simple reason is that this solution would be similar to what
DrRacket has and has had for a long time

So guile studio could play the simililarity card

What would be really required, here, is a consideration of which
population guile studio is meant for and then an investigation with
such population

But I understand that that's not within reach

Some years ago I was enabled to work on a little project in Clojure
thanks to a thing called "Emacs Live"

It's here
http://overtone.github.io/emacs-live/

it's a .emacs.d folder that you replace your one with

and it gives you a complete environement, based on Emacs, to work with
Clojure

With REPL, autocompletion and all the features of a modern IDE (we
should discuss what "modern" mean because the Smalltalk IDE was way
more modern than many IDEs for java these days)

So this idea of a distribution of Emacs taylored to introduce people to
Guile is a good idea

Kudos




      reply	other threads:[~2021-06-19  6:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  6:56 guile studio - question Adriano Peluso
2021-06-17 10:21 ` Ricardo Wurmus
2021-06-18  8:16   ` Adriano Peluso
2021-06-18  9:25     ` Ricardo Wurmus
2021-06-19  6:17       ` Adriano Peluso [this message]

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=fb7fb2c6efd3c1449568f9f7eaca0e401e9a1724.camel@riseup.net \
    --to=randomlooser@riseup.net \
    --cc=guile-user@gnu.org \
    --cc=rekado@elephly.net \
    /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).