I recently set UnicodeOutout=Yes and then got some very funny results.
I'm using "cmd /?" simply as a test program that generates text output.
This exists at least back to 4NT 6, and I don't understand why it
would behave this way. Appending to the clipboard appears to be
different than just writing to it. Using "LIST CLIP:" shows that the
first part of the file is Unicode (16 bit wide characters), but the
second half is ASCII (8 bit wide characters).
D:\>Option //UnicodeOutput=No
D:\>cmd /? > clip:
D:\>cmd /? >>clip:
D:\>*tail clip:
The completion code deals correctly with file names that contain spaces
or other special characters by placing quotes around the matching path.
Also, if you back up, then invoke completion from within a line, the
text to the right of the cursor at the point completion was invoked is
discarded.
The special characters that require quotes are:
<space>
&()[]{}^=;!'+,`~
However, when I set UnicodeOutput:
D:\>Option //UnicodeOutput=Yes
D:\>cmd /? > clip:
D:\>cmd /? >>clip:
D:\>*tail clip:
The completion code deals correctly with file names that contain spaces
or other special characters by placing quotes around the matching path.
Also, if you back up, then invoke completion from within a line, the
text to the right of the cursor at the point completion was invoked is
discarded.
The special characters that require quotes are:
<space>
&()[]{}^=;!'+,`~
??????????????????????????????????????????????????????????????????????+???????????????+++?????4????????????????????????????
++??????????????????????????????+++????????????????????????????????++?????????/++??????????????????????????????????+++?????
???4???????????????????????????++?????????????????????????????????+++????????+?????????????????????????????????????+???????
?????
etc.
--
Jim Cook
2008 Fridays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Saturday.
I'm using "cmd /?" simply as a test program that generates text output.
This exists at least back to 4NT 6, and I don't understand why it
would behave this way. Appending to the clipboard appears to be
different than just writing to it. Using "LIST CLIP:" shows that the
first part of the file is Unicode (16 bit wide characters), but the
second half is ASCII (8 bit wide characters).
D:\>Option //UnicodeOutput=No
D:\>cmd /? > clip:
D:\>cmd /? >>clip:
D:\>*tail clip:
The completion code deals correctly with file names that contain spaces
or other special characters by placing quotes around the matching path.
Also, if you back up, then invoke completion from within a line, the
text to the right of the cursor at the point completion was invoked is
discarded.
The special characters that require quotes are:
<space>
&()[]{}^=;!'+,`~
However, when I set UnicodeOutput:
D:\>Option //UnicodeOutput=Yes
D:\>cmd /? > clip:
D:\>cmd /? >>clip:
D:\>*tail clip:
The completion code deals correctly with file names that contain spaces
or other special characters by placing quotes around the matching path.
Also, if you back up, then invoke completion from within a line, the
text to the right of the cursor at the point completion was invoked is
discarded.
The special characters that require quotes are:
<space>
&()[]{}^=;!'+,`~
??????????????????????????????????????????????????????????????????????+???????????????+++?????4????????????????????????????
++??????????????????????????????+++????????????????????????????????++?????????/++??????????????????????????????????+++?????
???4???????????????????????????++?????????????????????????????????+++????????+?????????????????????????????????????+???????
?????
etc.
--
Jim Cook
2008 Fridays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Saturday.