Question about TPIPE and Pseudo Devices
- Thread starter Jay Sage
- Start date
- Jun
- 762
- 16
I just experimented a bit. At first it looked as though the other clipboards could be used for input, but that was misleading. One can specify a numbered clipboard, but the code actually uses CLIP: (i.e., CLIP0:) even if one specifies another clipboard. That really should be flagged as a syntax error.
Specifying TMP0: for the input did produce a syntax error message.
Specifying TMP0: for the input did produce a syntax error message.
rconn
Administrator
- May
- 13,695
- 257
Staff member
It would not be simple (or possible) to support CLIPn or TMPn. The TPIPE code is in a third-party dll (I do not have the source code).
The only way to do it would be to have TCC in the background dump the CLIPn and TMPn buffers to a temp disk file, have TPIPE read the disk file, and (if necessary) redirect the TPIPE output back to another temp file and then copy the contents of that file to the pseudodevice. Which is all way more complicated than is worthwhile for a single user request. And it's something you can do yourself.
rconn
Administrator
- May
- 13,695
- 257
Staff member
Not reproducible here; everything wraps as expected. (This would have to be a MS browser bug, since that's the rendering engine in use.)
- Jan
- 950
- 19
Not reproducible here too.
- Jun
- 762
- 16
That's fine. As you said, one can do it oneself with pipes. I'm just finding it very handy to use the TMP pseudo devices as temporary files, since one does not have to worry about cleaning up. I was going to update my mailmerge script to stop using temporary files. However, with judicious use of ON BREAK commands in the code, I seem to have managed to get all the temporary files deleted no matter how I terminate the script. So it really does not need to be updated.
You might want to change the syntax checking, however, to throw an error message if one tries to use CLIPn:. Otherwise one thinks it's working.
- Jan
- 950
- 19
+1 from me for that suggestion.
- Jun
- 762
- 16
As far as the TPIPE help is concerned, I see the same problem when I open on the online help using Firefox. It is with the material that opens for the /simple option.
That top line that fails to wrap once the window gets narrower than a critical with is in a paragraph with the following code:
The code doesn't look particularly different from the code for other text. But I don't understand why the paragraphs have varying margin styles. Nor do I see anything abnormal in the CSS file for the p_Normal class definition.
Now I just tried the same material in Chrome, and the problem appears there as well. And in Edge. And in Opera. So either there is something about the file, or all these browsers are getting some setting from my computer. Later I'll try with my laptop. Ah, I see the same problem on my Android phone using Chrome.
That top line that fails to wrap once the window gets narrower than a critical with is in a paragraph with the following code:
<p class="p_Normal" style="margin: 0 0 0 4.5625rem;">The code doesn't look particularly different from the code for other text. But I don't understand why the paragraphs have varying margin styles. Nor do I see anything abnormal in the CSS file for the p_Normal class definition.
Now I just tried the same material in Chrome, and the problem appears there as well. And in Edge. And in Opera. So either there is something about the file, or all these browsers are getting some setting from my computer. Later I'll try with my laptop. Ah, I see the same problem on my Android phone using Chrome.
- Jan
- 950
- 19
Just for info: I can't reproduce that with latest Firefox release ... hmm ... weird.
- Jan
- 950
- 19
It COULD be a general text size setting problem (system wide).