[CHANGESET] Documentation and behavior of read_readline_init_file are incoherent
John W. Eaton
jwe at bevo.che.wisc.edu
Mon May 5 02:23:43 CDT 2008
On 3-May-2008, Rafael Laboissiere wrote:
| The documentation of read_readline_init_file says:
|
| -- Built-in Function: read_readline_init_file (FILE)
| Read the readline library initialization file FILE. If FILE is
| omitted, read the default initialization file (normally
| `~/.inputrc').
|
| However, when the following commands are issued:
|
| octave:1> read_readline_init_file ("foo")
| octave:2> read_readline_init_file ()
|
| the second one will not read the default initialization file. Instead, it
| will reread "foo".
|
| The very trivial changeset attached below seems to fix the problem.
| However, I think that the following code in liboctave/oct-rl-edit.c:
|
| else
| rl_re_read_init_file (0, 0);
OK, I omitted this and the check on F (the rl_read_init_file function
can accept F == 0).
I also added a new re_read_readline_init_file function so we can
re-read the init file without having to know which one was actually
read the first time.
Thanks,
jwe
More information about the Bug-octave
mailing list