On 3/24/15, Chet Ramey wrote:
> There are a number of unjustified expectations here. The biggest is that
> readline can know about characters printed to the screen by another
> program. Readline expects to be able to use the entire line and that it
> begins with the cursor in column 0.
This can
On 3/24/15 1:54 AM, isabella parakiss wrote:
> rlwrap is a nice utility that enables readline's features in utilities
> that don't provide them. I tried to rewrite something similar in bash
> so here's a sketch of the code:
>
> while read -re; do
> history -p -- "$REPLY"
> history -s -- "$REP
On Tue, Mar 24, 2015 at 06:54:14AM +0100, isabella parakiss wrote:
> The problem is when I pipe that to a program that prints a prompt.
> In the examples, the prompt will be a $ and it will be printed by the
> second program in the pipeline.
There is no way readline (or whatever the first command
