Save To STDOUT from TCEdit

[Joe Caverly]

     _x64: 1
   _admin: 1
_elevated: 1

TCC  32.10.20 x64   Windows 10 [Version 10.0.19045.4291]
BuildNumber  Caption                   CSDVersion  OSArchitecture  Version
19045        Microsoft Windows 10 Pro              64-bit          10.0.19045

Well,
I'm pretty sure that I have done this before,
but I cannot remember exactly how to do it.

TMP9 contains several rows of text;

TMP9:
1963-04-20
1968-04-20
1974-04-20
1985-04-20
1991-04-20
1996-04-20
2002-04-20
2013-04-20
2019-04-20
2024-04-20

E:\Utils>type tmp9: | sort /r 
2024-04-20
2019-04-20
2013-04-20
2002-04-20
1996-04-20
1991-04-20
1985-04-20
1974-04-20
1968-04-20
1963-04-20

No problem so far.

Next,
open TMP9: in TCEdit,
make changes,
then Save to STDOUT;

Next, Exit TCEdit.

Both of these methods;

E:\Utils>tcedit tmp9: | sort /r

or

E:\Utils>type tmp9: | tcedit | sort /r

...produce no results to the console.

What exactly am I missing?

(NOTE: I'm just using Sort as an example command to demonstrate my problem.]

Joe

 

[vefatica]

TMP9: doesn't seem special. A command much like the example in the help (Save to STDOUT) does nothing. Have you ever seen "Save to STDOUT) do something?

v:\> dir /b | tcedit | grep btm

v:\>

 

[Joe Caverly]

I was pretty sure I used it when it was introduced.

I've tried it with TCC versions 28 to 32,
and no-go.

I cannot remember how I did this.

Hoping @rconn can advise.

Joe

 

[Joe Caverly]

Now I remember.

I was using the SPFLite2 Editor.

SPFLite2.exe -clip

...starts the editor with the clipboard contents.

When I use the SAVE command,
it automatically updates the Windows Clipboard
with the changes I have made.

So,
Save to STDOUT in TCEdit might just be non-conforming.

Thanks @vefatica for confirming the issue.

Joe

 

[samintz]

According to the help for TCEdit:
Piping Input to TCEdit

TCEdit supports piped input. For example, "dir | TCEdit" will load the contents of the directory into the first tab window.
TCEdit supports piped output with the "File / Write to STDOUT" menu option. This allows you to edit the pipe input before sending it on to be processed by another app. For example:

dir /b | tcedit | someapp

I tried all of these with "Write to STDOUT" :
path /n | tcedit | type @con
path /n | tcedit > foo.txt
path /n | tcedit | do p in @con (echo %p;)
And nothing produced any output

 

[samintz]

BTW - the menu choice is "Save to STDOUT", not "Write to STDOUT" as stated in the help.

this also produces nothing: path /n | tcedit | tcedit

 

[Phileosophos]

FWIW, I couldn't get the "Save to STDOUT" option to do anything in a simple pipe I put together either: dir | tcedit | sort