Clink ignores the standard readline init file (~/.inputrc)

[pahindman]

Clink can only be configured by either editing clink_inputrc_base in the clink installation dir, or clink_inputrc in the clink profile dir. It would be nice if clink could use the same readline configuration that other programs use.

[mridgers]

This is a little tricky as Clink's use of Readline is not necessarily compatible with other software that also uses Readline (escape sequences for special keys for example). Hence the "clink_" prefix. Not that the current way it currently works is particularly ideal.

[rivy]

Actually, IMO, it's not particularly ideal; using the default ".inputrc" file would be better and more compatible with other platforms.

As far as incompatibilities, the inputrc $if directive was specifically designed help with application variations. When using gnu readline, setting rl_readline_name sets the application name which can be used in the inputrc to customize behavior.

For example, set rl_readline_name to "CMD" (for example) and then the ".inputrc" file can be customized as needed by using:

... <common settings>
$if CMD
... <CMD settings>
$endif
... <more common settings>

Then a single inputrc file can be constructed which can be used for all shells.

[rivy]

👍