Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #169838 > unrolled thread

Turn on Echo in Terminal

Back to article view | Back to linux.debian.user

Contents

  Turn on Echo in Terminal Shelly Love <lb.fam@hotmail.com> - 2016-07-07 18:40 +0200
    Re: Turn on Echo in Terminal "Thomas Schmitt" <scdbackup@gmx.net> - 2016-07-07 19:30 +0200
    Re: Turn on Echo in Terminal David Wright <deblis@lionunicorn.co.uk> - 2016-07-07 20:10 +0200

#169838 — Turn on Echo in Terminal

[Multipart message — attachments visible in raw view] — view raw

Hello,


Commands I type in the terminal don't show, although the results occur.


So if I type "ls" I don't see "ls" but the directory listing is shown.


How do I enable?


I have tried


stty echo


and


reset and this hasn't worked.


Also saw this issue being discussed below, I am running Python on this server:


http://askubuntu.com/questions/171449/shell-does-not-show-typed-in-commands-reset-works-but-what-happened

[http://cdn.sstatic.net/Sites/askubuntu/img/apple-touch-icon@2.png?v=c492c9229955&a]<http://askubuntu.com/questions/171449/shell-does-not-show-typed-in-commands-reset-works-but-what-happened>

Shell does not show typed in commands, "reset" works, but ...<http://askubuntu.com/questions/171449/shell-does-not-show-typed-in-commands-reset-works-but-what-happened>
askubuntu.com
My problem is that the Bash shell stops showing the characters I type into it. It does read the commands though. I've come across this problem quite a few times and I ...

[toc] | [next] | [standalone]

#169839

Hi,

obviously the terminal emulation is messed up. Normally this happens
after a program, which can navigate over the whole terminal area, ended
without cleaning up the terminal settings.

The reciepe for reproducing the effect at
  http://askubuntu.com/questions/171449/shell-does-not-show-typed-in-commands-reset-works-but-what-happened
works for me. With:

  echo some_existing_file | xargs vim

vim warns

  Vim: Warning: Input is not from a terminal

and after it ends, the xterm (i.e. VT102 emulation) is in the problem state.
If i toggle in blindly

  stty sane

and press two times Return then i'm back to normal.
(The second Return is to get the shell prompt at the start of its own line.)

The diff of output of
  stty --all
shows ("<" sane, ">" insane):
-----------------------------------------------------------------------------
  < intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
  < eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
  < werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
  ---
  > intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof = <undef>;
  > eol = <undef>; eol2 = <undef>; swtch = <undef>; start = <undef>; stop = <undef>;
  > susp = <undef>; rprnt = <undef>; werase = <undef>; lnext = <undef>;
  > flush = <undef>; min = 0; time = 0;
  6,10c7,11
  < -ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -ixon -ixoff
  < -iuclc -ixany imaxbel -iutf8
  < opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
  < isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
  < echoctl echoke
  ---
  > -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff
  > -iuclc -ixany -imaxbel -iutf8
  > -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 > -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt
  > -echoctl -echoke
-----------------------------------------------------------------------------


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#169840

On Thu 07 Jul 2016 at 16:27:41 (+0000), Shelly Love wrote:
> Commands I type in the terminal don't show, although the results occur.
> So if I type "ls" I don't see "ls" but the directory listing is shown.
> How do I enable?
> I have tried
> stty echo
> and reset and this hasn't worked.

It might help to know:
Which terminal (a VC in the absence of X, an xterm, a VC while X is running...),
Did this happen right away with logging in,
How did you eventually recover (assuming you have),
What were you doing immediately before it happened.

As you can see from the references you gave, the reasons might
be more obvious once these factors are revealed.

(Note that reset can only work if typed at the shell prompt, not if
you're stuck inside some application.)

Cheers,
David.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web