octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54672] Odd behavior on first input


From: Michael Godfrey
Subject: [Octave-bug-tracker] [bug #54672] Odd behavior on first input
Date: Mon, 17 Sep 2018 10:59:20 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36

URL:
  <https://savannah.gnu.org/bugs/?54672>

                 Summary: Odd behavior on first input
                 Project: GNU Octave
            Submitted by: godfrey
            Submitted on: Mon 17 Sep 2018 02:59:19 PM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: Godfrey
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Since both the most recent build: 4e108574385c
and (as a possible cause the most recent Fedora 28 update)
when Octave is started in terminal mode only a few
characters are accepted, all others are rejected (and bell
rings). An accepted character is "c". After input of a string
of c's then CR, everything is normal. And, the same error
occurs in gui mode. I suspect that this is some quirk in
the latest Fedora updates, possibly related to Wayland stuff.
This is entirely a guess.

Has anyone else noticed this?




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?54672>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]