From: Fab on
Hello readers

I use a 64-bit Linux distribution with an AMD dual core. I usually
work with MATLAB in the command line. However, there is this weird
thing, that when I finish the MATLAB session and return to the shell
prompt (I use aterm and xterm) I can type any command but the shell
does not print to stdout anymore, so I do not see what I type. I never
had this problem on a 32bit machine. Does anybody know why that is, am
I missing a package?

Thank you
Fab
From: Walter Roberson on
Fab wrote:

> I use a 64-bit Linux distribution with an AMD dual core. I usually
> work with MATLAB in the command line. However, there is this weird
> thing, that when I finish the MATLAB session and return to the shell
> prompt (I use aterm and xterm) I can type any command but the shell
> does not print to stdout anymore, so I do not see what I type. I never
> had this problem on a 32bit machine. Does anybody know why that is, am
> I missing a package?

What happens if at the shell level, you (blindly) give the Linux command

stty echo

From: Fab on
On Jul 26, 11:34 pm, Walter Roberson <rober...(a)hushmail.com> wrote:
> Fab wrote:
> > I use a 64-bit Linux distribution with an AMD dual core. I usually
> > work with MATLAB in the command line. However, there is this weird
> > thing, that when I finish the MATLAB session and return to the shell
> > prompt (I use aterm and xterm) I can type any command but the shell
> > does not print to stdout anymore, so I do not see what I type. I never
> > had this problem on a 32bit machine. Does anybody know why that is, am
> > I missing a package?
>
> What happens if at the shell level, you (blindly) give the Linux command
>
> stty echo

This resolves my issue! Thanks Walter

could you please explain what I just did or why the MATLAB session
disables something in the settings?

Kind regards
Fab
From: Walter Roberson on
Fab wrote:
> On Jul 26, 11:34 pm, Walter Roberson <rober...(a)hushmail.com> wrote:
>> Fab wrote:
>>> I use a 64-bit Linux distribution with an AMD dual core. I usually
>>> work with MATLAB in the command line. However, there is this weird
>>> thing, that when I finish the MATLAB session and return to the shell
>>> prompt (I use aterm and xterm) I can type any command but the shell
>>> does not print to stdout anymore, so I do not see what I type. I never
>>> had this problem on a 32bit machine. Does anybody know why that is, am
>>> I missing a package?
>> What happens if at the shell level, you (blindly) give the Linux command
>>
>> stty echo
>
> This resolves my issue! Thanks Walter
>
> could you please explain what I just did or why the MATLAB session
> disables something in the settings?

I don't know why it is happening to you. Typically this sort of thing
happens when a program takes over control of a terminal (e.g., so that
it can handle in-line user editing itself) and then the program crashes
before restoring the previous settings.

stty echo

tells the system to turn character echoing back on for the current input
stream.

I could refer you to the details of what stty does and how terminal
input is handled in Unix, but really it wouldn't help much at all in
understanding _why_ this is happening.
From: Fab on
On Jul 27, 4:23 pm, Walter Roberson <rober...(a)hushmail.com> wrote:
> Fab wrote:
> > On Jul 26, 11:34 pm, Walter Roberson <rober...(a)hushmail.com> wrote:
> >> Fab wrote:
> >>> I use a 64-bit Linux distribution with an AMD dual core. I usually
> >>> work with MATLAB in the command line. However, there is this weird
> >>> thing, that when I finish the MATLAB session and return to the shell
> >>> prompt (I use aterm and xterm) I can type any command but the shell
> >>> does not print to stdout anymore, so I do not see what I type. I never
> >>> had this problem on a 32bit machine. Does anybody know why that is, am
> >>> I missing a package?
> >> What happens if at the shell level, you (blindly) give the Linux command
>
> >> stty echo
>
> > This resolves my issue! Thanks Walter
>
> > could you please explain what I just did or why the MATLAB session
> > disables something in the settings?
>
> I don't know why it is happening to you. Typically this sort of thing
> happens when a program takes over control of a terminal (e.g., so that
> it can handle in-line user editing itself) and then the program crashes
> before restoring the previous settings.
>
> stty echo
>
> tells the system to turn character echoing back on for the current input
> stream.
>
> I could refer you to the details of what stty does and how terminal
> input is handled in Unix, but really it wouldn't help much at all in
> understanding _why_ this is happening.

gotcha! Anyway, thanks for your help. I've added stty echo at the end
of my matlab alias and it resolves my issue like I want it to.

Best,
Fab
 |  Next  |  Last
Pages: 1 2
Prev: MCR Backward compatibility
Next: Divergence application