From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: readline eats previous text on line
Date: Fri, 06 Oct 2006 00:35:05 +0100 [thread overview]
Message-ID: <878xju1gly.fsf@ossau.uklinux.net> (raw)
In-Reply-To: 87bqoujltw.fsf@zip.com.au
Kevin Ryde <user42@zip.com.au> writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>>
>> Slightly confusingly, set-readline-prompt! does also set the default
>> prompt for an explicit `readline' call (1). I think the overall
>> situation would be clearer if it didn't.
>
> It's not too terrible, may as well leave it alone in case anyone's
> nutted it out and is using it.
OK, agreed.
>> The bug which Jon has noted, about the effect of set-readline-prompt!
>> not lasting very long, is caused by the fact that Guile's REPL code,
>
> It might have been from only using `display' to show a prompt, which
> readline doesn't know and hence overwrites.
Good point. I believe Jon's going to raise this (inability to do
readline starting from the column after the prompt) with the readline
people.
>> ... This code should instead
>> save the existing prompts and restore them afterwards
>
> But yes, that'd be a good thing.
>
>> Patch is below.
>
> Looks pretty reasonable.
Thanks; I've committed it now.
Regards,
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-10-05 23:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 21:26 readline eats previous text on line Jon Wilson
2006-09-28 1:40 ` Kevin Ryde
2006-09-28 1:50 ` Jon Wilson
2006-09-28 7:49 ` Neil Jerram
2006-09-29 0:47 ` Kevin Ryde
2006-09-29 22:33 ` Neil Jerram
2006-09-30 12:25 ` Neil Jerram
2006-10-03 0:15 ` Kevin Ryde
2006-10-03 0:52 ` Kevin Ryde
2006-10-04 23:13 ` Kevin Ryde
2006-10-05 23:06 ` Neil Jerram
2006-10-05 23:35 ` Neil Jerram [this message]
2006-10-06 0:03 ` Kevin Ryde
2006-12-01 20:24 ` Jon Wilson
2006-10-03 0:22 ` Kevin Ryde
2006-09-28 21:08 ` Jon Wilson
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=878xju1gly.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@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).