From: Nala Ginrut <nalaginrut@gmail.com>
To: Matthew Keeter <matt.j.keeter@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Readline behavior with colored custom prompt
Date: Fri, 26 Feb 2016 13:09:06 +0800 [thread overview]
Message-ID: <1456463346.7330.53.camel@Renee-desktop.suse> (raw)
In-Reply-To: <ABCC8C42-9759-4B71-9906-6DF6BB0A3C3C@gmail.com>
Are you looking for something like guile-colorized?
https://github.com/NalaGinrut/guile-colorized
On Thu, 2016-02-25 at 12:20 -0500, Matthew Keeter wrote:
> Hi all,
>
> I’m seeing strange behavior with readline's interaction with ANSI codes.
>
> Here’s a minimal sample script that reproduces the behavior:
>
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> (use-modules (system repl repl) (system repl common))
> (use-modules (ice-9 readline))
>
> (define (custom-prompt repl) "\x1b[34m :D > \x1b[0m")
>
> (activate-readline)
> (repl-default-option-set! 'prompt custom-prompt)
>
> (start-repl)
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>
> Run this and you’ll get a Guile shell. Into that shell, type
>
> '(1 2 3 4 5 6 7 8 9 10)
>
> The final parenthesis will highlight a character midway through the string
> (instead of the first parenthesis).
>
> The same issues happen if you try to scroll through history: lines end up
> overlapping in strange ways.
>
> Removing the ANSI codes from custom-prompt resolves the issue, but I’d really
> like to have a colored prompt and correct readline behavior.
>
> Does anyone have any ideas?
>
> Thanks,
> Matt
prev parent reply other threads:[~2016-02-26 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 17:20 Readline behavior with colored custom prompt Matthew Keeter
2016-02-25 18:05 ` Mike Gran
2016-02-25 18:53 ` Matthew Keeter
2016-02-25 22:09 ` Matthew Keeter
2016-02-26 5:09 ` Nala Ginrut [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=1456463346.7330.53.camel@Renee-desktop.suse \
--to=nalaginrut@gmail.com \
--cc=guile-user@gnu.org \
--cc=matt.j.keeter@gmail.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).