Done TEE to tmp:

[Joe Caverly]

My suggestion is to update the TEE command to copy stdin
to one of the 10 TMP: pseudo character devices

Example:

echo %StockTicker,%Rating | tee /a tmp8:

Joe

 

[Joe Caverly]

V33 says that TEE can now write to the TMPn: pseudo-devices.

E:\Utils>tmp 
TMP0:
TMP1:
TMP2:
TMP3:
TMP4:
TMP5:
TMP6:
TMP7:
TMP8:
TMP9:

E:\Utils>echo %_date %_time | tee /a tmp9:
2024-09-14 13:19:39

E:\Utils>tmp 
TMP0:
TMP1:
TMP2:
TMP3:
TMP4:
TMP5:
TMP6:
TMP7:
TMP8:
TMP9:

Would someone please verify if this works for them,
as it does not work for me.

Joe

 

[Jay Sage]

I can confirm that it does not work with the TMP pseudo-devices. It does work with CLIP: but not with CLIP#: (except for # = 0).

 

[Joe Caverly]

This works...

echo %_date %_time |! tee /a tmp9:

Ref: https://jpsoft.com/forums/threads/tee-to-tmp.12071/post-69596

Joe

 

[Jay Sage]

Of course! Pipes no longer run in the current session, and TMP and CLIP pseudo-devices are local to their session. For someone who does not use pipes very often, this is hard to remember.

It's probably too much to ask that TCC detect a TMP or CLIP destination and automatically use an in-process pipe. That may not be easy to do.

In my case, I'd probably prefer to have pipes default to the in-process version and require the '!' character to use the new pipe. Rex would probably have a good reason not to provide that as an option.

 

[rconn]

Of course! Pipes no longer run in the current session, and TMP and CLIP pseudo-devices are local to their session. For someone who does not use pipes very often, this is hard to remember.

It's probably too much to ask that TCC detect a TMP or CLIP destination and automatically use an in-process pipe. That may not be easy to do.

That would be impossible - TCC does not do any processing on the command line following the pipe character. That is the responsibility of the child process (which might be something completely different and incompatible with TCC syntax).

In my case, I'd probably prefer to have pipes default to the in-process version and require the '!' character to use the new pipe. Rex would probably have a good reason not to provide that as an option.

It would be a compatibility disaster.