unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Bernardo Ezequiel Contreras <vonbecmann@gmail.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Anniversary hack: Zile editor with Guile support
Date: Mon, 13 Feb 2012 11:25:17 -0300	[thread overview]
Message-ID: <CAHCRasmUpyeSFkcLWPe0J-R9p2rCNvQ6HTJn7U94vYFe5GYw0Q@mail.gmail.com> (raw)
In-Reply-To: <1329094293.53143.YahooMailNeo@web37901.mail.mud.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]

Do you plan to write everything on guile? is it possible?

On Sun, Feb 12, 2012 at 9:51 PM, Mike Gran <spk121@yahoo.com> wrote:

>
>
> Hello-
>
> In response to Ludo's request for a Guile-2.0 anniversary hack, I'll
> start by offering a release of a hack I made.  But this isn't my
> official hack: it is just a building block.
>
> Zile-on-Guile is a version of GNU Zile that uses GNU Guile as an
> extension language.  The original GNU Zile was a small editor in the
> style of GNU Emacs and it has its own tiny embedded Lisp interpreter.
> I've replaced that interpreter with Guile.
>
> You can find the download at
>
> https://github.com/downloads/spk121/zile/zile-on-guile-0.0.tar.gz
>
> This is a 0.0 release, so if it even builds on anyone else's machine,
> I'd be totally surprised.
>
> You can find the Git repository at
>
> https://github.com/spk121/zile
>
> The Guile extension can be accessed this way.
>
> -- Pressing Alt+C brings up a REPL.  You can do all your standard REPL
>    things.
>
> -- In the REPL, one can create and bind new commands.  Define a
>    procedure of zero arguments, export it, and then bind it to a key
>    using 'set-key'.
>
>    For example:
>
>      (define (blammo)
>        (insert "blammo"))
>      (export blammo)
>      (set-key "\\F9" 'blammo)
>
>    This creates a function that inserts the world "blammo" at the mark
>    whenever <F9> is pressed.
>
> -- And, if really you wanted to, you could edit your current buffer in
>    the REPL
>
>    For example:
>
>       (insert "here is some text")
>       (forward-char)
>
>    But that would just be silly.
>
> Thanks,
>
> Mike Gran
>
>

[-- Attachment #2: Type: text/html, Size: 2302 bytes --]

  reply	other threads:[~2012-02-13 14:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  0:51 Anniversary hack: Zile editor with Guile support Mike Gran
2012-02-13 14:25 ` Bernardo Ezequiel Contreras [this message]
2012-02-13 15:37   ` Mike Gran
2012-02-13 22:40     ` Ludovic Courtès
2012-02-13 14:27 ` Ludovic Courtès
2012-02-14  5:46   ` Mike Gran
     [not found] <CAOnWdoggx6YWV_VUuYcdosvsXFwYXzua57NaUTa7ZT3RiUtvOA@mail.gmail.com>
     [not found] ` <4CB5C160-9728-4784-ABA1-E8BDFC825990@vaughan.pe>
2013-03-22  1:13   ` Gary V. Vaughan
2013-03-22  2:43     ` Mike Gran
2013-03-22  3:10       ` Gary V. Vaughan
2013-03-25  2:13         ` Ian Price
2013-03-25  2:21           ` Gary V. Vaughan
2013-03-25  4:10             ` Ian Price
2013-03-25  4:22               ` Gary V. Vaughan
2013-03-25  6:24                 ` Ian Price
2013-03-25  7:06                   ` Gary V. Vaughan
2013-03-25  2:52           ` Nala Ginrut
2013-03-22 11:05     ` Ludovic Courtès
2013-03-23  1:32       ` Nala Ginrut

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=CAHCRasmUpyeSFkcLWPe0J-R9p2rCNvQ6HTJn7U94vYFe5GYw0Q@mail.gmail.com \
    --to=vonbecmann@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=spk121@yahoo.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).