Skip to main content
Expansion of last question
Source Link
aliceinpalth
  • 1.7k
  • 14
  • 18

Settings that are in the .inputrc file affect all programs that use the GNU readline library, not just bash. Think of the .inputrc file as being a configuration file for GNU Readline similar to how .bashrc is a configuration file for bash.

GNU Readline is described as:

... A set of functions for use by applications that allow users to edit command lines as they are typed in.

To clarify a bit further, settings that are in the .bashrc file only affect bash. If you'd like to optionally run bash without GNU Readline support or usage, you can invoke bash with the --noediting option as follows: bash --noediting. You can find out more about bash options here.

To answer your last question of

How do I distinguish when to put what where?

If you'd like an option to affect all programs on your system that use the GNU Readline library, .inputrc would be the prime choice. Elsewise, if you simply want to configure your bash session, .bashrc would be the best choice.

Settings that are in the .inputrc file affect all programs that use the GNU readline library, not just bash. Think of the .inputrc file as being a configuration file for GNU Readline similar to how .bashrc is a configuration file for bash.

GNU Readline is described as:

... A set of functions for use by applications that allow users to edit command lines as they are typed in.

To clarify a bit further, settings that are in the .bashrc file only affect bash. If you'd like to optionally run bash without GNU Readline support or usage, you can invoke bash with the --noediting option as follows: bash --noediting. You can find out more about bash options here.

Settings that are in the .inputrc file affect all programs that use the GNU readline library, not just bash. Think of the .inputrc file as being a configuration file for GNU Readline similar to how .bashrc is a configuration file for bash.

GNU Readline is described as:

... A set of functions for use by applications that allow users to edit command lines as they are typed in.

To clarify a bit further, settings that are in the .bashrc file only affect bash. If you'd like to optionally run bash without GNU Readline support or usage, you can invoke bash with the --noediting option as follows: bash --noediting. You can find out more about bash options here.

To answer your last question of

How do I distinguish when to put what where?

If you'd like an option to affect all programs on your system that use the GNU Readline library, .inputrc would be the prime choice. Elsewise, if you simply want to configure your bash session, .bashrc would be the best choice.

Source Link
aliceinpalth
  • 1.7k
  • 14
  • 18

Settings that are in the .inputrc file affect all programs that use the GNU readline library, not just bash. Think of the .inputrc file as being a configuration file for GNU Readline similar to how .bashrc is a configuration file for bash.

GNU Readline is described as:

... A set of functions for use by applications that allow users to edit command lines as they are typed in.

To clarify a bit further, settings that are in the .bashrc file only affect bash. If you'd like to optionally run bash without GNU Readline support or usage, you can invoke bash with the --noediting option as follows: bash --noediting. You can find out more about bash options here.