On Sat, Feb 08, 2025 at 04:59:51PM -0500, Paul Fox wrote:
> brendan wrote:
> > I've not had problems with bracketed-paste myself, zsh in rxvt-unicode
> > with vile has worked fine for me: I get bracketed paste at the
> > command-line (pastes show up in reverse video, and newlines are not
> > interpreted until you actually hit enter), and vile doesn't get sent the
> > escape characters. vile in xterm also seems fine.
>
> Thank you for that. If I slowly, patiently, and without anger :-)
> perform the same experiment with bash (first enabling bracketed paste
> in .inputrc, where it's usually disabled), then all of that works fine
> for me, as well, and just as you describe.
>
> I hadn't previously understood that the shell would only enable b-p
> while at the command prompt. That makes perfect sense, but the
> descriptions of the feature always leave out that detail.
>
I was the original question asker in this long thread. All the more
recent discussion has, I think, explained to me why it just happens
sometimes.
I have turned off bracketed paste on my systems by putting:-
set enable-bracketed-paste off
in a custom .inputrc file. Thus the problems with vile mostly don't
occur.
However I **haven't** turned off bracketed paste for root so I think
that's when I get bitten, having logged in to root to do somwthing and
then back out again.
I had been fixing the problem, when it occurred, by simply doing
'reset' in the terminal window. I now think I may turn bracketed past
off system wide, it's nothing but a nuisance!
--
Chris Green
