Follow-up Comment #5, bug #13249 (project screen):
If you can provide any details then please do.
distribution
screen version
terminal emulator (and version of it) you use
how big selection are we talking about? (xclip -o |wc -c)
does string you paste contain any special characters?
how are you p
Follow-up Comment #5, bug #47247 (project screen):
This behaviour was introduced by:
http://git.savannah.gnu.org/cgit/screen.git/commit/?h=screen-v4&id=98b6b4105b60150c5bf9d022b2e7de698a62a797
to me parsing passed stuff makes sense, hence the need for double escaping
things.
___
Update of bug #49883 (project screen):
Status:None => Need Info
___
Follow-up Comment #1:
Hello,
can you add
altscreen on
to your .screenrc and check if you still have problems. Seems to
Follow-up Comment #6, bug #47247 (project screen):
OK, I have a workflow that involves sending text to an application running in
a screen session. I don't know what your use-case is, and I would like to hear
more about it and what your code is doing. But given that users can run
virtually anything
Follow-up Comment #2, bug #49883 (project screen):
Thanks, now described bugs disappeared.
But now appeared that tmux bug I just described as "be careful not to
introduce". I will try to repeat it simpler.
* Start screen (with altscreen on)
* Type into it: "for ((I = 1; I <= 100; ++I)) { echo $I;
