From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Can `make tags' generate tags for Scheme source, as well as C?
Date: Mon, 11 Oct 2010 22:38:04 +0100 [thread overview]
Message-ID: <87pqvgpg03.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87hbh1a8l1.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 05 Oct 2010 00:36:58 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Hi Neil,
>
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> BTW, ‘M-.’ in Geiser works really great, if you haven’t tried yet. And
>>> it works across all the modules currently loaded, not just those of the
>>> current project.
>>
>> I think I must be missing something: for me it always says "Couldn't
>> find edit location for X" in the echo area.
>
> Make sure to compile the source file with C-c C-k first.
OK, I wasn't doing that.
> And before
> that, make sure to have a suitable ‘geiser-guile-load-path’.
What would be the right value, for a top level script file? (i.e. one
with no define-module form)
> Does C-c d RET in a Scheme buffer work for you?
No, but C-c C-d RET does. I guess that's what you meant.
Thanks,
Neil
next prev parent reply other threads:[~2010-10-11 21:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 17:47 Can `make tags' generate tags for Scheme source, as well as C? Neil Jerram
2010-09-12 11:35 ` Andy Wingo
2010-09-15 14:37 ` Ludovic Courtès
2010-10-04 22:00 ` Neil Jerram
2010-10-04 22:36 ` Ludovic Courtès
2010-10-11 21:38 ` Neil Jerram [this message]
2010-10-04 22:40 ` Jose A. Ortega Ruiz
2010-10-11 21:41 ` Neil Jerram
2010-10-11 22:11 ` Andy Wingo
2010-10-11 22:24 ` Jose A. Ortega Ruiz
2010-10-12 9:36 ` Andy Wingo
2010-10-12 12:12 ` Jose A. Ortega Ruiz
2010-10-12 17:46 ` Andy Wingo
2010-10-12 18:03 ` Jose A. Ortega Ruiz
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=87pqvgpg03.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@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).