- Jun
- 568
- 4
1. The help file entry for the TYPE command should be updated to mention that it works not only with CLIP: but with the numbered clipboards as well.
2. The help should somewhere note that redirection is not protected with the clipboards. One can enter a command such as
and the text will replace what was already in clipn:, even if that clipboard had not been empty and redirection protection was configured to be on.
3. Perhaps it is obvious, but it might be worth noting also that text can be appended to a clipboard using
4. The help notes that the @LINES function can be used with the clipboards. However, it appears to me that the two variables that are supposed to be returned by the function (namely %_lines_maxlen and %_lines_maxloc) do not work. Indeed, the values remain what they were the last time that @LINES was used with an actual file. That's too bad, because I had already thought of a use for them with the clipboards. Rex, is that a bug that can be fixed?
5. I just noticed a slight mistake/confusion in the help for the @CLIPWN function. The syntax and the example have a space after the comma. If there is such a space, it becomes part of the clipboard contents as a leading space. The syntax should be
The example is technically OK but will put " save this line" (without quotes) into the clipboard. The help says that the function returns 0 if the write was successful. Just curious: How could it not be successful? Anything wrong I tried produced a syntax error message and did not run the command line. Of course, the function has to return something, and it is good to be told what it is.
I'm coming to appreciate that these extra clipboards can be very useful. They have a lot of the convenience of temporary files without the need to avoid name conflicts and the risk of leaving clutter behind. And they don't have to be pre-dimensioned like arrays.
2. The help should somewhere note that redirection is not protected with the clipboards. One can enter a command such as
echo New clipboard text > clipn:
and the text will replace what was already in clipn:, even if that clipboard had not been empty and redirection protection was configured to be on.
3. Perhaps it is obvious, but it might be worth noting also that text can be appended to a clipboard using
echo More clipboard text >> clipn:
4. The help notes that the @LINES function can be used with the clipboards. However, it appears to me that the two variables that are supposed to be returned by the function (namely %_lines_maxlen and %_lines_maxloc) do not work. Indeed, the values remain what they were the last time that @LINES was used with an actual file. That's too bad, because I had already thought of a use for them with the clipboards. Rex, is that a bug that can be fixed?
5. I just noticed a slight mistake/confusion in the help for the @CLIPWN function. The syntax and the example have a space after the comma. If there is such a space, it becomes part of the clipboard contents as a leading space. The syntax should be
@CLIPWN[clipboard,string]
The example is technically OK but will put " save this line" (without quotes) into the clipboard. The help says that the function returns 0 if the write was successful. Just curious: How could it not be successful? Anything wrong I tried produced a syntax error message and did not run the command line. Of course, the function has to return something, and it is good to be told what it is.
I'm coming to appreciate that these extra clipboards can be very useful. They have a lot of the convenience of temporary files without the need to avoid name conflicts and the risk of leaving clutter behind. And they don't have to be pre-dimensioned like arrays.