[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 300 baud V.21 terminal emulation
From: |
Mike Miller |
Subject: |
Re: 300 baud V.21 terminal emulation |
Date: |
Fri, 4 Oct 2013 07:37:49 -0400 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Fri, Oct 04, 2013 at 02:29:09 -0500, Daniel J Sebald wrote:
> From that it seems Octave can then modify blink-matching behavior
> without having to relaunch the terminal (or Octave). The steps
> would be something like:
>
> 1) Octave looks for, say, .octaveinputrc. If it doesn't exist,
> create it with the contents
>
> set blink-matching-paren off
Octave already installs its own inputrc. Look in scripts/startup. You
can try adding whatever commands you want there.
> 2) Octave sets the environment variable INPUTRC to .octaveinputrc
> before launching the terminal emulator.
No need because of the above. Also wrong, INPUTRC is a user environment
variable, programs should never override that.
> 3) In Octave's options, if the user changes the setting for
> blink-matching, Octave can simply change .octaveinputrc to
>
> set blink-matching-paren off
>
> and then force a Ctrl-x Ctrl-r into the terminal emulator to make it
> reread .octaveinputrc.
I believe Octave's own inputrc is already read after any default inputrc
files when readline is initialized. Any extra effort to force another
reload of the settings is unnecessary. Even if the user does change the
setting, programs should not try to override that because they think
they know better.
You can certainly try adding this directive to Octave's inputrc and see
if it helps, but don't do anything like trying to force a reload to
override user prefs.
--
mike