From: ludo@gnu.org (Ludovic Courtès)
To: Shane Celis <shane.celis@gmail.com>
Cc: Guile Mailing List <guile-user@gnu.org>, BT Templeton <bpt@hcoop.net>
Subject: Re: GSoC: Guile-Emacs + Emacsy
Date: Thu, 06 Jun 2013 22:45:39 +0200 [thread overview]
Message-ID: <87k3m7q87g.fsf@gnu.org> (raw)
In-Reply-To: <496709D4-531F-429B-B14C-B2C697FD3BD3@gmail.com> (Shane Celis's message of "Thu, 6 Jun 2013 12:42:00 -0400")
Hello!
(Stripping emacs-devel here.)
Shane Celis <shane.celis@gmail.com> skribis:
> I've written up a blog post[1] on some of the features and ideas that
> I've been turning over in my head for how best to go about providing
> online help such that an Emacsy app can be self-documenting, job
> control, and a note about the key-lookup-command-execute-loop. I
> could certainly use input from Guilers and Emacsers about how best to
> achieve these things.
[...]
> [1]:
> http://shanecelis.github.io/emacsy/2013/06/05/google-summer-of-code-2013-emacsy/
This looks promising.
Regarding documentation, using Guile’s built-in web server seems like
the least intrusive mechanism, from an application developer’s
viewpoint, and it should work well in practice (using Guile’s web
server, SXML, and Texinfo modules.)
I was thinking that perhaps Emacsy could also offer a GTK+ mode, where
it would display documentation in a GTK+ window instead (perhaps using
Guile-GNOME). A few years ago Andy had written a Texinfo browser for
Guile-GNOME, which could give some ideas [0].
WDYT?
Job control would seem like a very nice feature. I’m not sure what the
API could you like (esp. assuming it uses cooperative threads), but it’s
a good idea to dig further in that direction.
Thanks,
Ludo’.
[0] http://wingolog.org/archives/2004/07/25/literate-programming-with-guile-lib
prev parent reply other threads:[~2013-06-06 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 12:10 GSoC: Guile-Emacs + Emacsy Ludovic Courtès
2013-05-28 13:47 ` Grant Rettke
2013-05-28 17:21 ` Aurélien Aptel
2013-06-04 3:15 ` Noah Lavine
2013-06-06 16:42 ` Shane Celis
2013-06-06 20:45 ` Ludovic Courtès [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=87k3m7q87g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bpt@hcoop.net \
--cc=guile-user@gnu.org \
--cc=shane.celis@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).