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

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

[Octave-bug-tracker] [bug #56079] Command window does not accept letters


From: anonymous
Subject: [Octave-bug-tracker] [bug #56079] Command window does not accept letters "a", "p", or "w"
Date: Fri, 5 Apr 2019 12:16:22 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0

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

                 Summary: Command window does not accept letters "a", "p", or
"w"
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Fri 05 Apr 2019 04:16:21 PM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: Gordon Chamberlain
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 5.1.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

Under Windows 7, using Octave Version 5.1.0.0, in the GUI environment with a
separate command window, typing the letters "a", "p", or "w", no letters show
and they are not accepted.  These letters are behaving as if they are a
"control" or "escape" sequence and are not accepted as character input.  For
example, when I'm trying to type "pkg load mapping", the following occurs:


>> kg lod ming
error: 'kg' undefined near line 1 column 1
>>


As you can see, the letters "a" and "p" simply do not appear and are not
accepted as input.

If I use the function kbhit (still in the command window under GUI execution),
the letters (a/p/w) do get properly returned as output results.

So the error seems to be in the interpreter's parsing of the input line in the
separate command window under GUI execution.  




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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