From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org, Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Can `make tags' generate tags for Scheme source, as well as C?
Date: Tue, 12 Oct 2010 14:12:30 +0200 [thread overview]
Message-ID: <8739sbehjl.fsf@newton.homeunix.net> (raw)
In-Reply-To: <m38w23da6x.fsf@unquote.localdomain> (Andy Wingo's message of "Tue, 12 Oct 2010 11:36:38 +0200")
On Tue, Oct 12 2010, Andy Wingo wrote:
[...]
>> Expecting anything to work in Geiser before starting (or connecting to)
>> a REPL is a bad expectation, yes :)
>
> Could it ask to start a new Guile or connect to a Guile?
Every time you try a geiser command without an active REPL, there's an
error message in the echo area saying
"No Geiser REPL for this buffer (try M-x run-geiser)"
If that message wasn't displayed in Neil's case, that's a bug.
>> I don't think it's a good a idea to load modules behind the user's
>> back.
>
> Could it ask? :-)
It could, but it's a lot of work :-) It can also be annoying to keep
answering questions: i'd need to keep track of whether i've already
asked, options would be needed to deactivate the behaviour, to make
auto-loading the default... more work... I think i'd need one or two
more users feeling the need for this feature (i don't) :-).
next prev parent reply other threads:[~2010-10-12 12:12 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
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 [this message]
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=8739sbehjl.fsf@newton.homeunix.net \
--to=jao@gnu.org \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
--cc=wingo@pobox.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).