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 *can* intentionally break vile, by executing: > :!printf "\e[?2004h" > after which the escape characters turn up when pasting in vile. Yes, that work (i.e. breaks) for me as well. > One kludge you could consider if you're having the issue is to just have > vile eat the sequences. I couldn't work out how to map! to an empty > string, but adding these to .vilerc seems to work OK for my limited > testing: > map! ^[[200~ ^[a > map! ^[[201~ ^[a Thank you! I'd forgotten that map/map! is so literal in what it will accept. That will certainly help. As you say, mapping to null would be better yet. Maybe Tom knows how to do that. I certainly don't remember. But really, vile should learn how to handle bracketed paste on its own. Maybe I'd learn to love it! I wish I understood what has been happening to enable b-p without me knowing how. It's also happened recently to my wife, as well, so there may be something common in our environment that's causing it. It's disabled in every login shell we each use, so it's a bit of a mystery. Two things that could definitely cause it: if you have a shell which enables it, and that shell is either SIGKILLed, or its machine suspends and your ssh connection is lost after some time, then in either case your terminal will be left with b-p enabled. The latter happens to me fairly often, but since the machine that suspends has b-p disabled, I don't think that's the culprit. I'll try and pay more attention. paul =---------------------- paul fox, [email protected] (arlington, ma, where it's 31.5 degrees)
