-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
9term: pasted buffer does not show when reading stdin #55
Comments
not seen on linux 3.2.29, x.org 1.12.3, twm. |
Reproducible here using 9term, bash and rio. I don't know if the same happens with rc. Linux 4.3.3 (x86_64) |
On openbsd, the bug does not happen if using the rc shell |
ah. :) yes i have seen this before. bash, ksh, and i imagine most other shells put the terminal into raw mode. you'll want to select 'cook' from the mb2 menu to get them to play nice. or, the shells themselves may have some option, or there may be some suitable setting for $TERM. edit: i posted without thinking. i'm not sure why you all have problems. if i start |
Indeed, if I select the "cook" mode the problem goes away. Also, $TERM is set to 'dumb' by default under 9term. If I set it to say, vt100, the problem also goes away. But I am pretty sure having the apps believe they are running under vt100 when we are under 9term is not the best idea. Any suggestion about some suitable $TERM value so that I don't have to select "cook" every time? |
hmm, interestingly there is the "9term" option under the possible $TERM values. But still, it does not make the bug here related go away. Although it seem to fix some things. For example, if I open "top" under 9term with $TERM set to "dumb", the terminal just closes. Whereas if I set $TERM to "9term", it presents an correct output. |
It looks like this behaviour is documented on 9term man page:
set +o emacs #fixed the problem here |
Since I didn't find a way to automate "set +o emacs" (putting it on my .profile wasn't enough), I ended up setting SHELL=rc on my .profile so that 9term uses the rc shell instead of ksh. |
i always use it with rc. i set $SHELL in my i'm generally happy with chording cut/paste rather than using history, and i prefer rc's syntax for lots of things. i make functions for oft-repeated commands. you may however wish to |
C11 is apparently too new for these systems. Fixes #55.
If you paste something on a 9term while a program is reading STDIN, the value will be pasted but won't be shown on the terminal. The bug does not happen if something was previously typed manually before pasting.
How to reproduce:
The text won't show on the terminal. But it is there, and if you press ENTER cat will echo it. Also, if you type anything after you started the program reading STDIN but before pasting, then the pasted text will show normally.
Tested on openbsd 5.9, under both fvwm, rio and dwm window managers. Using ksh shell.
The text was updated successfully, but these errors were encountered: