[Octave-bug-tracker] [bug #56079] Command window does not accept letters "a", "p", or "w"

[Gordon Chamberlain]

Follow-up Comment #3, bug #56079 (project octave):

Thanks for the quick response to my problem.

1. Does the problem not show up with a command window 
docked to the main window?

The problem persists even when the command window is
docked to the main window.


2. Do you have some readline configuration in the .octaverc file?

OK.  This lead to the solution for fixing the problem:

Under the new Octave 5.1.0 installation under Windows 7, the following are the
paths created for system configuration files:

  D:\Octave\Octave-5.1.0.0\ming64\share\octave\site\m\startup\octaverc

And, also the following paths:

  D:\Octave\Octave-5.1.0.0\ming64\share\octave\5.1.0\m\startup\octaverc
with the accompanying path
  D:\Octave\Octave-5.1.0.0\ming64\share\octave\5.1.0\m\startup\inputrc

(NOTE:  Under Octave 4.4.0, the path to octaverc did not have the additional 
"\ming64\"  directory level.)
  
In the "5.1.0\m\startup" path, in the octaverc file, I saw the following
comment:

## Re-read user's personal inputrc to give precedence over Octave's default.

So, I thought this was a good way to place user input in a convenient place
for adding to the startup process without having to change the octaverc file
itself.

So, that was the problem.  With the following lines added to the "inputrc"
file:

addpath('D:\\OCTAVE\\GeoGraphs\\Georgia\\');
pkg load io
pkg load geometry
pkg load mapping
warning ('off', 'Octave:data-file-in-path');

You get the strange a/p/w input problems.  (Why?  I'll leave that problem
alone.)

Removing those lines and everything goes back to normal.  I now see that the
"inputrc" file is only  intended for user configuration relative to the GNU
Readline library.

I also found that adding my startup commands to either one of the octaverc
files (different paths) seems to work (without having to change the
OCTAVE_VERSION_INITFILE environment variable).

So, I'm back to placing my startup commands into the octaverc file here:
  D:\Octave\Octave-5.1.0.0\ming64\share\octave\site\m\startup\octaverc
  
and, getting back to my real machine learning programming projects.

Thanks for the suggestions that lead me to finding the solution.

This problem can be closed for my purposes.

(By the way, when initially invoked, the new 5.1.0 version starts up much
faster!)

    _______________________________________________________

Reply to this item at:

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

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