From: Andy Wingo <wingo@pobox.com>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
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 19:46:09 +0200 [thread overview]
Message-ID: <m3zkujb8ym.fsf@unquote.localdomain> (raw)
In-Reply-To: <8739sbehjl.fsf@newton.homeunix.net> (Jose A. Ortega Ruiz's message of "Tue, 12 Oct 2010 14:12:30 +0200")
On Tue 12 Oct 2010 14:12, "Jose A. Ortega Ruiz" <jao@gnu.org> writes:
> "No Geiser REPL for this buffer (try M-x run-geiser)"
Yes, I get this at times. But why tell me what to do? Why not do it for
me, with my permission? A single keypress keeps you in flow.
>>> 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) :-).
Fair enough :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-10-12 17:46 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
2010-10-12 17:46 ` Andy Wingo [this message]
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=m3zkujb8ym.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).