>> set +o emacs
>> set +o vi
>>
>> to turn off those editing modes, bash will just read from the
>> tty with echo turned on
>
> Is that to say that readline turns echo off when typing?
yes.
> If, for example, the emacs keybindings are set, there may be another way
> to insert that initial
Russ Cox writes:
> set +o emacs
> set +o vi
>
> to turn off those editing modes, bash will just read from the
> tty with echo turned on
Is that to say that readline turns echo off when typing?
If, for example, the emacs keybindings are set, there may be another way
to insert that initia
> Enabling cooked mode (middle-click -> 'cook', probably
> along with `stty -echo`) can help -- it makes 9term only
> send an entire line at once -- but it may create some other problems.
A better way to do this is to leave 9term in nocook mode
(meaning the menu says cook - just don't click on it)
> bash/readline does not know what you click on -- it still thinks you are
> typing at the end of line.
> Mantas Mikulėnas (0xD24F6CB2C1B52632)
Aha! Thanks for the explanation. I completely 'missed' that readline
reads as I type...
Now it makes some sense.
R
On Wed, 26 Jan 2011 13:21:10 +0100, Rudolf Sykora wrote:
> in linux I often start programs from a terminal running bash like
> this
> ; (program &)
> which somehow achieves to run the program in the background and the
> program further survives the terminal's end.
It's called "double-fork", AFAIK
