unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-devel@gnu.org
Subject: Re: file names embedded in .go
Date: Wed, 21 Apr 2010 09:45:43 +0200	[thread overview]
Message-ID: <87eii9ckpk.fsf@ambire.localdomain> (raw)
In-Reply-To: <8739yqhr5e.fsf@newton.homeunix.net> (Jose A. Ortega Ruiz's message of "Tue, 20 Apr 2010 21:15:25 +0200")

() "Jose A. Ortega Ruiz" <jao@gnu.org>
() Tue, 20 Apr 2010 21:15:25 +0200

   It's an Emacs environment for Scheme similar to Slime: a repl and a
   bunch of utilities to edit, navigate and obtain information about the
   code. Among them, jumping to an identifier's definition: for that, i
   need guile to tell me where in the file system the identifier is bound.
   Geiser does not usually collect metadata on the elisp side, relying on
   the running guile to provide it. The richer that dynamic metadata is,
   the more functionality Geiser can provide.

   A bit more information is available at http://gitorious.org/geiser and
   links thereof (specially the README; no real documentation yet, i'm
   afraid).

Thanks for the pointer.  I'll take a look next time on the net.

I think (designing out loud) programs like Geiser will have no problem
if they use Emacs' features that support "virtually located" files.
See ‘file-name-handler-alist’, for the most fundamental mechanism.

Of course the inferior Guile needs to provide a clean syntax that doesn't
conflict with other subsystems.  There are basically two approaches: work on
top of something else (best candidate: TRAMP), or sidestep all others.

Programs that don't build on Emacs are another matter, but who in their
right mind goes outside Emacs?  ;-)

thi




  reply	other threads:[~2010-04-21  7:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 14:52 file names embedded in .go Andy Wingo
2010-04-19 21:46 ` Thien-Thi Nguyen
2010-04-20  0:08   ` Jose A. Ortega Ruiz
2010-04-20 11:35     ` Thien-Thi Nguyen
2010-04-20 19:15       ` Jose A. Ortega Ruiz
2010-04-21  7:45         ` Thien-Thi Nguyen [this message]
2010-04-20  9:45   ` Andy Wingo
2010-04-20 10:34     ` Thien-Thi Nguyen
2010-04-19 23:12 ` port-filename and path canonicalization Ludovic Courtès
2010-04-20  9:42   ` Andy Wingo
2010-04-20 11:15     ` Thien-Thi Nguyen
2010-04-21  8:49       ` Ludovic Courtès
2010-04-21 19:16         ` Thien-Thi Nguyen
2010-04-21 22:26           ` Ludovic Courtès
2010-04-22  7:42             ` Thien-Thi Nguyen
2010-04-20 16:57     ` Ludovic Courtès
2010-04-22 11:10       ` Andy Wingo
2010-04-22 12:50         ` Ludovic Courtès
2010-04-19 23:23 ` file names embedded in .go Ludovic Courtès

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=87eii9ckpk.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --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).