maybe sub'ing them away, or making it print \\e instead \e On Fri, Jan 21, 2022, 09:24 Lawrence Velázquez <v...@larryv.me> wrote:
> On Fri, Jan 21, 2022, at 12:22 AM, L A Walsh wrote: > > On 2022/01/18 22:31, Alex fxmbsw7 Ratchev wrote > >>> Fix: > >>> Haven't looked deeply into the bash internals but sanitizing the > directory > >>> name (along with other user-controlled substitutions in the prompt) > should > >>> work. > >>> > > Sanitizing? What's that? > > Especially in a way that won't break existing legal usages? > > Curious what "existing legal usages" there are for allowing a change > of working directory to result in arbitrary escape sequences being > sent to your terminal. > > -- > vq > >
