[Top][All Lists]

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

Re: inputrc issue

From: Mike Miller
Subject: Re: inputrc issue
Date: Sun, 16 Oct 2005 20:34:17 -0500 (CDT)

On Sun, 16 Oct 2005, John W. Eaton wrote:

On 16-Oct-2005, Mike Miller wrote:

| So doesn't this mean that Octave is only reading /etc/inputrc and not
| reading ~/.inputrc?

Are there no other lines in the strace output for the .inputrc file in your home directory? Here is what I see on my system:

I do not see that unless I have it in my startup/octaverc. When I have the appropriate lines in startup/octaverc, I see this in strace:

{st_mode=S_IFREG|0644, st_size=63, ...}) = 0
open("/home/mbmiller/local/share/octave/2.1.71/m/startup/inputrc", O_RDONLY) = 4
stat64("/home/mbmiller/.inputrc", {st_mode=S_IFREG|0640, st_size=63, ...}) = 0
open("/home/mbmiller/.inputrc", O_RDONLY) = 4

Is it possible you your HOME environment variable is set inccorrectly?

I don't think so. "echo $HOME" works fine from the command prompt before I type "octave".

I am satisfied with what I have now. I'm using the ~/local/share/octave/2.1.71/m/startup/octaverc to control access to inputrc files and it works fine. If you want more help figuring out what is going wrong, I'm happy to oblige.

Maybe it has to do with my use of ./configure --prefix=/home/mbmiller/local
Is that possible? Maybe not everything in Octave is following the prefix correctly. Otherwise, I think my installation is pretty ordinary.


Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

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