[9fans] p9p 9term problem

[9fans] p9p 9term problem

[Rudolf Sykora]

Hello,

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.

When I write the command I often forget to write the opening '('. So,
in 9term, I click at the line beginning, add the '(', click at the
line end, hit enter. And I see:

bash: syntax error near unexpected token `)'

although the line looks correct --- when I highlight it and 'send', it works.

Something goes wrong...
Is it just my problem?

Thanks
Ruda

Re: [9fans] p9p 9term problem

[Mantas Mikulėnas]

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.

You can also use `disown` (as in `program & disown`) to achieve the same thing.

> When I write the command I often forget to write the opening '('. So,
> in 9term, I click at the line beginning, add the '(', click at the
> line end, hit enter. And I see:
>
> bash: syntax error near unexpected token `)'
>
> although the line looks correct --- when I highlight it and 'send',
> it works.

bash/readline does not know what you click on -- it still thinks you are typing at the end of line.

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.

--
Mantas Mikulėnas (0xD24F6CB2C1B52632)

Re: [9fans] p9p 9term problem

[Rudolf Sykora]

> 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

Re: [9fans] p9p 9term problem

[Russ Cox]

> 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).
As long as you execute (for bash)

    set +o emacs
    set +o vi

to turn off those editing modes, bash will just read from the
tty with echo turned on, and if echo is turned on 9term will
let you do mouse editing and deliver the lines one line at
a time.

Even better, at least for acme users, is that win works with
stty echo turned on too.  In fact it works better.  It does the
echo cancellation internally (if it sees echoing coming back
it just doesn't print it) and automatically erases typing after
a prompt like

    Password:

so you can run ssh or sudo in a win window without fear
of displaying your password for all to see.

This is all as of mid-October 2010.  If you haven't updated
since then you might want to.

Russ

Re: [9fans] p9p 9term problem

[smiley]

Russ Cox <rsc@swtch.com> 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 initial parenthesis: ^A ( ^E

Wouldn't that work, too?

But I might call more of a workaround than a fix.

Re: [9fans] p9p 9term problem

[Russ Cox]

>>     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 parenthesis: ^A ( ^E
>
> Wouldn't that work, too?

yes but the original poster asked to be able
to use 9term's mouse editing.  if you want
^A ( ^E then my advice does not apply.

russ