unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
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 20:03:18 +0200	[thread overview]
Message-ID: <87y6a3cmqh.fsf@newton.homeunix.net> (raw)
In-Reply-To: <m3zkujb8ym.fsf@unquote.localdomain> (Andy Wingo's message of "Tue, 12 Oct 2010 19:46:09 +0200")

On Tue, Oct 12 2010, Andy Wingo wrote:

> 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.

Because perhaps you don't want to do it, and keep asking would be
annoying. So it'd have to remember not to ask again, and then, if after
10 warnings you decide you want to do it, you'll have to do it anyway.
But if you're sure you don't want it, perhaps you'll want to deactivate
the warnings... and that's all state that is associated with buffers and
will have to be inherited for buffers visiting the same file, or perhaps
not (let's put there another option); and then the state will get stale
and newbies will get confused, and have to read the manual two or three
times to understand all the available options.

Typing 'M-x run-geiser' (or binding that to a function key) once before
you start hacking scheme keeps you in flow for the rest of your emacs
instance life much more simply... :)



      reply	other threads:[~2010-10-12 18:03 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
2010-10-12 18:03                   ` Jose A. Ortega Ruiz [this message]

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=87y6a3cmqh.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).