I am having a bit of rookie trouble getting the shell output to a file.

What I see in the documentation is:

command > file /A

This only generates an empty file. I have tried creating the file first. I have tried >> to append the file.

In my instance, I want to direct the output of the command "chelp all" to a file so I can print it.

Please let me know what I am missing.

Code:

[ Editiert durch Amigaharry2 31.01.2026 - 08:02 ]

Odd, I still get an empty file when trying the code below.

I am using the command "chelp all" and would like to have the output stored in a file for easy reference.

TIA for any help!

-E


Quote:

What is "chelp"? What does chelp print in console?

Quote:

Likely this command is printing the output to standard error. You can redirect standard error to file with:

Code:

You can also send both standard output and standard error to same file by using *>< for example:
Code:

I successfully made a file with the output from an different command (devlist) so my issue has been solved.

devlist >Ram:devlist.txt

Chelp is a CLI program to provide command descriptions in the shell. It appears that it pulls the command descriptions from a network connection. I suspect this must be my problem getting the output to a file. The chelp output is likely directed TO the shell and the redirect simply doesn't capture any of the data as I assumed it would.

I didn't really have much need to redirect data to a file until I saw the size of the "chelp all" output. Of course, I picked a command that has a caveat to sending it's output to a file.... I am happy enough just learning about this and will hopefully stumble on an explanation in my future learning.

Thanks for your help!

Quote:

Quote:
It is my script, but can't remember details how it works now :) I can check it better when I'm back home next days.

But for printable material check its cache dir.
HELP:english/Shell/ by default iirc. Shell_commands.txt or so.

jPV, nice work on Chelp!

Indeed, chelp places the data I need to print into Ram:T/Chelp_temp/Shell_Commands.txt

As I'm learning more about shell commands, of course I chose Chelp for a quick reference in the shell for commands. It was just coincidence that I chose "chelp all" as the specimen for me to redirect the output. I do see the .lua file to have a look at so I will see what I can glean from it.

All good, thanks guys!

-E



Quote:

More about this...

Chelp is a shell ("AmigaDOS") script that has the Script protection bit set and it can be launched just like a command. It's only a helper script that actually calls LuaX and the main Lua script.

I'm not sure if you can redirect a shell script output to a file at all... anyone remembers or has any tips?

Basically if you launch a shell script with the Execute command, only Execute's own output (errors mainly) will be redirected to a file, but it seems that nothing that the given script does is redirected. It usually calls external programs that might output something, but it isn't catched with a rediretion of the main Execute command.

In this particular case you could redirect output of the Lua script if you launch it by LuaX yourself, skipping the shell script completely...

BTW. if you want to read loong outputs in the shell window, you can pause the output by pressing some key that enters a character into the shell, and continue by erasing the character then. I usually press the space bar for that, and continue with the backspace. But of course MorphOS has the scrollback buffer also, so it's not that important trick as it used to be on Amiga :)

And you can also save the shell output to a file from the Review menu in the Shell window if you can't use redirection for some reason.

jPV,

Thank you very much for the explanation. It all makes sense now, but at the moment I tried the redirect, it was surely a mystery.

This script impresses me for it's (usefulness &) ability to use a network connection. I'll get on with my shell learning for now and then have a look at this gem!

Cheers,

-E



Quote:

Quote:

Thanks, I think it's pretty cool myself too :) The network part is made with wget nowadays, but it used to be with the TCP: device without any external dependencies at first. The TCP: device solution didn't support the HTTPS protocol where MorphOS Library moved at some point, so I changed it to wget. The Library seems to work with HTTP again nowadays, so it could be possible to revert back, but I don't know if that's necessary after all.