unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neiljerram@googlemail.com>
Cc: 12207@debbugs.gnu.org
Subject: bug#12207: repl and comments or tabs
Date: Mon, 20 Jun 2016 21:39:03 +0200	[thread overview]
Message-ID: <87bn2v8xbc.fsf@pobox.com> (raw)
In-Reply-To: <87txw3lxuz.fsf@pobox.com> (Andy Wingo's message of "Wed, 15 Aug 2012 22:11:00 +0200")

A very kind ping :)

You didn't sign up to do this but maybe you would like to do it?  I'll
never know if I don't ask :)

Hope you are well, & happy hacking :)

Andy

On Wed 15 Aug 2012 22:11, Andy Wingo <wingo@pobox.com> writes:

> Hi Neil,
>
> Mailing you since you were the last to touch the REPL, and perhaps you
> have a desire for a small hack :)
>
> There are two bugs that bother me off and on.  One is that pasting
> Scheme code into the Guile REPL can cause autocompletion if the Scheme
> code has tabs for whitespace.  I wonder, is there a way to fix that?
>
> Another is that going up into the history where the history has
> multi-line Scheme expressions with comments doesn't work, because a
> comment from line N will cause lines N+1,N+2... to be commented out --
> because they all end up on the same line.  Is there a way for the
> history to preserve the multi-line nature of the input while only having
> one prompt?  Dunno, just a thought.
>
> Hope all is well.  Let me know if you are interested in these bugs.
>
> Cheers,
>
> Andy





  reply	other threads:[~2016-06-20 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 20:11 bug#12207: repl and comments or tabs Andy Wingo
2016-06-20 19:39 ` Andy Wingo [this message]
2016-07-28 17:21 ` helpful.user
2016-08-04 20:55   ` Andy Wingo
2017-05-17 20:30     ` 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=87bn2v8xbc.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=12207@debbugs.gnu.org \
    --cc=neiljerram@googlemail.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).