MXE: qt error with native build

classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Fixed [Re: MXE: qt error with native build]

Michael Goffioul
On Fri, Jun 21, 2013 at 7:06 AM, Philip Nienhuis <[hidden email]> wrote:
Michael Goffioul wrote:
On Fri, Jun 21, 2013 at 6:53 AM, John D <[hidden email]
<mailto:[hidden email]>> wrote:

    __ __

    __ __

    *From:* Michael Goffioul [mailto:[hidden email]
    <mailto:[hidden email]>]
    *Sent:* Friday, June 21, 2013 6:44 AM
    *To:* Philip Nienhuis
    *Cc:* John D; John W. Eaton; Octave Maintainers List
    *Subject:* Re: Fixed [Re: MXE: qt error with native build]____
    On Fri, Jun 21, 2013 at 4:56 AM, Philip Nienhuis
    <[hidden email] <mailto:[hidden email]>> wrote:____

        Of course there are some remaining things:

        - Octave starts off with a "-K>>" prompt (JD I think you
        mentioned this) and no blinking cursor (bug #39259)____

    Do you start octave from the MSYS shell?____

    If you do, try to unset TERM variable, like: TERM= octave.exe
<JD:>

    Unsetting term works for me____

The problem is that octave inherits TERM from the shell, I think it's
set to something like cygwin or rxvt (I don't remember). And readline
then starts sending control sequences that are not understood by the
windows terminal.

The -[K>> prompt doesn't appear in octave-cli. It's only an issue in the GUI command window (and only before the first command is entered.)

Does that still fit the picture?

What you're seeing is the sequence \E[K (\E stands for ESC), in cygwin terminal, this sequence is mapped to clear-to-end-of-line function. So yes, it still fits the picture. Note that if you start using the prompt, you'll see some other funny behavior. For instance try to type a long line, then move your cursor in the middle, and start adding new characters. Or try using the history browsing (assuming Up/Down keys are mapped to history search functions).

Michael.

Reply | Threaded
Open this post in threaded view
|

Re: Fixed [Re: MXE: qt error with native build]

Michael Goffioul
On Fri, Jun 21, 2013 at 7:14 AM, Michael Goffioul <[hidden email]> wrote:
On Fri, Jun 21, 2013 at 7:06 AM, Philip Nienhuis <[hidden email]> wrote:
Michael Goffioul wrote:
On Fri, Jun 21, 2013 at 6:53 AM, John D <[hidden email]
<mailto:[hidden email]>> wrote:

    __ __

    __ __

    *From:* Michael Goffioul [mailto:[hidden email]
    <mailto:[hidden email]>]
    *Sent:* Friday, June 21, 2013 6:44 AM
    *To:* Philip Nienhuis
    *Cc:* John D; John W. Eaton; Octave Maintainers List
    *Subject:* Re: Fixed [Re: MXE: qt error with native build]____
    On Fri, Jun 21, 2013 at 4:56 AM, Philip Nienhuis
    <[hidden email] <mailto:[hidden email]>> wrote:____

        Of course there are some remaining things:

        - Octave starts off with a "-K>>" prompt (JD I think you
        mentioned this) and no blinking cursor (bug #39259)____

    Do you start octave from the MSYS shell?____

    If you do, try to unset TERM variable, like: TERM= octave.exe
<JD:>

    Unsetting term works for me____

The problem is that octave inherits TERM from the shell, I think it's
set to something like cygwin or rxvt (I don't remember). And readline
then starts sending control sequences that are not understood by the
windows terminal.

The -[K>> prompt doesn't appear in octave-cli. It's only an issue in the GUI command window (and only before the first command is entered.)

Does that still fit the picture?

When you run octave-cli, you're running it inside the MSYS shell, which is able to interpret "cygwin" terminal control sequence (hence it defines TERM=cygwin).

Michael.

Reply | Threaded
Open this post in threaded view
|

RE: Fixed [Re: MXE: qt error with native build]

John Donoghue-3

 

 

From: Michael Goffioul [mailto:[hidden email]]
Sent: Friday, June 21, 2013 7:17 AM
To: Philip Nienhuis
Cc: John D; John W. Eaton; Octave Maintainers List
Subject: Re: Fixed [Re: MXE: qt error with native build]

 

On Fri, Jun 21, 2013 at 7:14 AM, Michael Goffioul <[hidden email]> wrote:

On Fri, Jun 21, 2013 at 7:06 AM, Philip Nienhuis <[hidden email]> wrote:

Michael Goffioul wrote:

On Fri, Jun 21, 2013 at 6:53 AM, John D <[hidden email]
<mailto:[hidden email]>> wrote:

    __ __

    __ __

    *From:* Michael Goffioul [mailto:[hidden email]
    <mailto:[hidden email]>]
    *Sent:* Friday, June 21, 2013 6:44 AM
    *To:* Philip Nienhuis
    *Cc:* John D; John W. Eaton; Octave Maintainers List
    *Subject:* Re: Fixed [Re: MXE: qt error with native build]____
    On Fri, Jun 21, 2013 at 4:56 AM, Philip Nienhuis
    <[hidden email] <mailto:[hidden email]>> wrote:____

        Of course there are some remaining things:

        - Octave starts off with a "-K>>" prompt (JD I think you
        mentioned this) and no blinking cursor (bug #39259)____

    Do you start octave from the MSYS shell?____

    If you do, try to unset TERM variable, like: TERM= octave.exe

<JD:>


    Unsetting term works for me____


The problem is that octave inherits TERM from the shell, I think it's
set to something like cygwin or rxvt (I don't remember). And readline
then starts sending control sequences that are not understood by the
windows terminal.


The -[K>> prompt doesn't appear in octave-cli. It's only an issue in the GUI command window (and only before the first command is entered.)

Does that still fit the picture?

 

When you run octave-cli, you're running it inside the MSYS shell, which is able to interpret "cygwin" terminal control sequence (hence it defines TERM=cygwin).

 

Michael.

 


Unsetting the term variable also fixes the line edit/refresh issues that I was seeing in the terminal window.

12