OK, in the end the unicode solution was a shell-related fluke, but replacing all double backslashes by 4 backslashes does work.
On Wed, Feb 24, 2016 at 9:17 PM, Max Rozenoer <astgt...@alum.mit.edu> wrote: > Looks like I found a workaround, replacing double backslashes by backslash > unicode pair >>> \u005c\u005c <<< appears to work. > > On Wed, Feb 24, 2016 at 9:10 PM, Max Rozenoer <astgt...@alum.mit.edu> > wrote: > >> Hi, all, >> >> In Screen v4.3.1 (and also v4.2.1) on Mac OS X, I am unable to send >>> >> -X stuff \\ <<< (double backslash) - nothing appears in the target window. >> In v4.00.03 (FAU) 23-Oct-06 (which shipped with Mac OS), this sequence >> sends just fine and shows up as >>> \ <<< (single backslash). >> >> This is not mere curiosity for me - I am working on a dev environment >> window manager which sends fairly complicated shell-escaped commands into >> the window, which sometimes result in sequences of backslashes. >> >> Any workarounds much appreciated! >> >> >
_______________________________________________ screen-users mailing list screen-users@gnu.org https://lists.gnu.org/mailman/listinfo/screen-users
