From: Andy Wingo <wingo@pobox.com>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: problem with trailing comment in repl
Date: Sat, 12 Feb 2011 13:34:03 +0100 [thread overview]
Message-ID: <m37hd5bfes.fsf@unquote.localdomain> (raw)
In-Reply-To: <87r5beb7dg.fsf@gnu.org> (Jose A. Ortega Ruiz's message of "Fri, 11 Feb 2011 22:15:23 +0100")
On Fri 11 Feb 2011 22:15, "Jose A. Ortega Ruiz" <jao@gnu.org> writes:
> scheme@(guile-user)> (define a 3) ;; foo
> <- cursor stays here; no prompt
>
> is that intended? i'm hoping it is not, because it confuses geiser, who
> is waiting for a new prompt to mark the end of the transaction.
It would be nice if there were a prompt in this case. However, it is
difficult to do. Because this case is very much like:
guile> (define a 3) (
<- no prompt, waiting for you to finish the expression
Or indeed, like:
guile> ;; foo
<- no prompt
After reading an expression, the REPL reader flushes any available
whitespace, then goes into a new read. If there are characters waiting
on the current input port, as they are if there is more than one
expression on one line, no prompt is printed. In this case we flush the
whitespace, and start reading at the ";", and keep on reading in the
next line.
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-02-12 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 21:15 problem with trailing comment in repl Jose A. Ortega Ruiz
2011-02-12 12:34 ` Andy Wingo [this message]
2011-02-12 13:21 ` Jose A. Ortega Ruiz
2011-02-12 14:36 ` Andy Wingo
2011-02-13 15:22 ` Noah Lavine
2011-02-13 19:19 ` Andy Wingo
2011-02-13 21:27 ` Noah Lavine
2011-02-14 10:09 ` Ludovic Courtès
2011-02-15 2:42 ` Noah Lavine
2011-03-03 22:56 ` Andy Wingo
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=m37hd5bfes.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=jao@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).