ba05d01476
As of readline 8.1, "bracketed paste" is enabled by default. However, the feature causes control characters to appear in captured (telnet) session output. This can throw off pattern matching if the output is to be processed by scripts. Let's keep the previous default of leaving this feature disabled and provide a configuration option for users to enable it. Signed-off-by: Markus Mayer <mmayer@broadcom.com> [yann.morin.1998@free.fr: - explicit enable/disable - no indentation in conditional block - rewrap help text ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
28 lines
950 B
Plaintext
28 lines
950 B
Plaintext
config BR2_PACKAGE_READLINE
|
|
bool "readline"
|
|
select BR2_PACKAGE_NCURSES
|
|
help
|
|
The GNU Readline library provides a set of functions for use
|
|
by applications that allow users to edit command lines
|
|
as they are typed in.
|
|
|
|
https://tiswww.case.edu/php/chet/readline/rltop.html
|
|
|
|
config BR2_PACKAGE_READLINE_BRACKETED_PASTE
|
|
bool "Enable bracketed paste"
|
|
depends on BR2_PACKAGE_READLINE
|
|
help
|
|
Enable the "bracketed paste" feature in libreadline.
|
|
|
|
Bracketed paste is helpful for interactive sessions when
|
|
one wants to prevent pasted text from being interpreted
|
|
as typed-in commands. However, it also causes control
|
|
characters to show up in the raw output of a (telnet)
|
|
session. This can cause issues and throw off pattern
|
|
matching if the session output is being captured for
|
|
automated processing.
|
|
|
|
For further information on this feature and whether you
|
|
may want it, see:
|
|
https://cirw.in/blog/bracketed-paste
|