Samuel Thibault, le dim. 27 avril 2025 12:45:04 +0200, a ecrit: > Samuel Thibault, le dim. 27 avril 2025 12:42:46 +0200, a ecrit: > > Samuel Thibault, le dim. 27 avril 2025 12:11:31 +0200, a ecrit: > > > Martin-Éric Racine, le dim. 27 avril 2025 11:29:21 +0300, a ecrit: > > > > then we're stuck with a command line that barfs > > > > on bash's standard command prompt's escape codes. > > > > > > I have seen that recently indeed. > > > > > > Contribution welcome. > > > > A quick grep in the bash source shows > > > > ./lib/readline/rlprivate.h:#define BRACK_PASTE_INIT "\033[?2004h" > > ./lib/readline/rlprivate.h:#define BRACK_PASTE_FINI "\033[?2004l\r" > > > > i.e. hardcoded constants, which does not make sense at all. > > > > That should be discussed with bash maintainers. > > (I see various people on the Internet advising to disable bracketed > paste, but that's bogus, it should just be fixed once and for all in > bash, not patched over by everybody in the world)
I eventually just made gnumach ignore any sequence it doesn't support rather than printing it. Having bash avoid spitting sequences at random would still be useful for the broad world. Samuel
