unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Jon Wilson <j85wilson@fastmail.fm>
Subject: Re: idea: create module
Date: Wed, 26 Apr 2006 08:51:20 -0500	[thread overview]
Message-ID: <444F7AD8.3040007@fastmail.fm> (raw)
In-Reply-To: <8764kxp87s.fsf@ossau.uklinux.net>

Hi Thien and Neil,
Those both sound like good solutions.  However, I was thinking of something 
within the language itself, rather than something outside, like emacs. 
This is partly because I don't use emacs, myself, and I am not particularly 
familiar with its capabilities versus vim.  Heck, I'm not sufficiently 
familiar with vim's capabilities, either, regardless that I use it every day.

I still think that something within the language would be useful, but 
perhaps I'm the only one, and thus should write it myself. :-p  Thanks for 
the good ideas, though!
Regards,
Jon

Neil Jerram wrote:
> "Jon Wilson" <j85wilson@fastmail.fm> writes:
> 
> 
>>Hi all,
>>I just had a random idea, and thought I'd run it by y'all.  What if you
>>could compose modules from the REPL, and then write them to a file? 
> 
> 
> Or alternatively you could write some Emacs Scheme mode support to
> allow you to evaluate definitions and expressions as you are writing
> ... which is what the "gds" stuff in my guile-debugging package does.
> 
> (Or at least aims to do; please let me know if you try it out and find
> that it doesn't work for you.)
> 
> Regards,
>     Neil
> 


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2006-04-26 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25  1:31 idea: create module Jon Wilson
2006-04-25  7:09 ` Thien-Thi Nguyen
2006-04-25 23:05 ` Neil Jerram
2006-04-26 13:51   ` Jon Wilson [this message]
2006-04-27  7:42     ` Neil Jerram
2006-05-02  4:08       ` Jon Wilson

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=444F7AD8.3040007@fastmail.fm \
    --to=j85wilson@fastmail.fm \
    /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).