From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: "Jose A. Ortega Ruiz" <jao@gnu.org>, guile-devel@gnu.org
Subject: Re: Can `make tags' generate tags for Scheme source, as well as C?
Date: Tue, 12 Oct 2010 00:11:09 +0200 [thread overview]
Message-ID: <m3d3rgcrcy.fsf@unquote.localdomain> (raw)
In-Reply-To: <87lj64pfto.fsf@ossau.uklinux.net> (Neil Jerram's message of "Mon, 11 Oct 2010 22:41:55 +0100")
On Mon 11 Oct 2010 23:41, Neil Jerram <neil@ossau.uklinux.net> writes:
> "Jose A. Ortega Ruiz" <jao@gnu.org> writes:
>
>> On Tue, Oct 05 2010, Neil Jerram wrote:
>>
>>> ludo@gnu.org (Ludovic Courtès) writes:
>>>
>>>> BTW, ‘M-.’ in Geiser works really great
>>>
>>> I think I must be missing something: for me it always says "Couldn't
>>> find edit location for X" in the echo area.
>>
>> b) for procedures in modules not yet loaded.
>
> I'm sorry, I think I was being a bit stupid - expecting that it would
> work even before starting a REPL.
Is this a bad expectation? It is the first impression.
If your source code is loaded it is autocompiled and you should find the
edit locations, but if they is not loaded, are the module headers enough
to autoload the needed pieces?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-10-11 22:11 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
2010-10-04 22:40 ` Jose A. Ortega Ruiz
2010-10-11 21:41 ` Neil Jerram
2010-10-11 22:11 ` Andy Wingo [this message]
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=m3d3rgcrcy.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=jao@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).